Welcome back to the dramatic conclusion of our discussion on the 12 factor app. This time we're talking dev/prod parity, logs, and admin processes. Oh, and Call of Duty!

It's time for more DevOps fun as we continue learning about the Twelve-Factor app. This week we dive into the next three chapters: port binding, concurrency, and disposability.

The holidays are coming sooner than we realized, so we gotta get our wish lists together. After all, no one wants to sit around the Festivus Pole without their favorite dev toys. This week we discuss some of the toys we love, as well as the ones we drool over, and even the ones we're not so crazy about.

Surveys – Wow we forget about them and ramble...sorry guys!

Mark Tinsley – PHP Composer – thanks for the tip!
https://getcomposer.org/

Joe made a game in Javascript (using dozens of libraries):

Box Pusher! (game name of the year)
https://github.com/THEjoezack/BoxPusher

Allen's cry for writing black-boxed, encapsulated code...
Episode on Encapsulation: http://www.codingblocks.net/episode23

Episode on SOLID Design: http://www.codingblocks.net/episode7

Probably want to listen to the first three parts of the 12 Factor App if you missed it:

http://www.codingblocks.net/episode32

IV. Backing Services

• Any resource consumed over the network: databases, mail servers, cloud services, etc.

• Anything external to your app (but could be local to your environment)

• Should not have to change any code to redeploy – should be config changes if anything

• Clearly Tech – Importance Rating: High

We've mentioned Splunk, and if you're not familiar, it's an enterprise piece of software that will aggregate logs from multiple sources (servers, computers, etc):
http://www.splunk.com/en_us/products/splunk-enterprise.html

Bug in Visual Studio that cost one person $6,500 in a few hours:

https://www.humankode.com/security/how-a-bug-in-visual-studio-2015-exposed-my-source-code-on-github-and-cost-me-6500-in-a-few-hours

V. Build, Release, Run

• Build stage – transform which converts the code repo into an executable bundle

• Release stage – combines the build with the required config and deposits it somewhere

• Run – runs the app in the execution environment (development, staging, production, other)

• Rolling back may be more complicated when you start talking about database schemas / data changes

• Clearly Tech – Importance Rating: Conceptual???

Version numbers? What do you prefer? Version numbers with major and minor revisions? Or do you prefer timestamps?

VI. Processes

• Stateless and Share Nothing

  • No local session

  • Make sure saving files go to an available repository

• Clearly Tech – Importance Rating: High (Joe wants higher than high)

Resources We Like

• http://www.12factor.net

• http://www.clearlytech.com/2014/01/04/12-factor-apps-plain-english/

• http://devcenter.heroku.com/articles/architecting-apps

   

Tips

Allen: Find problematic queries that are killing your SQL Server...replace 123 with the spid from sp_who2.

sp_who2 'active'

DBCC INPUTBUFFER(123)

If you want to be mean....replace 123 with the spid from sp_who2

KILL 123

Additionally, if there's high CPU and low I/O, it's likely either a missing or a fragmented index.

Joe: Tortoise Git

https://tortoisegit.org/

Mike: Tip of the week is the Pseudocode podcast
http://pseudocode.fm/

And...don't be lazy. We can't seem to get off our tails and get a business card made!

Dipping our toes into the DevOps waters with the Twelve-Factor App. How important is depedency management, and how fired would you be if you accidently leaked your company's source code?

In this episode we dive into Javascript Promises.  If you’re used to the olden way of doing an async call with a callback, you’ll definitely want to give this episode a listen as you could improve your mental sanity 10 fold by learning how to use promises in your application!

Part 4 of our design patterns series, this time up it's Adapters, Facades, and Mementos. Oh, an which tech luminary would make the best head of state!

This week we answer a question, Allen registers for school, Joe reads some numbers, Michael breaks out the survey results, and Joe cringes at the thought of bidets. It's time for episode 29! And we thought, what better to talk about than to continue our discussion on hierarchical data solutions.

So, how DO you persist hierarchical Data? We discuss two common solutions to this age-old problem: Adjacency Lists and Nested Set Models. Also, Build Atlanta, technical problems, multi-monitor vs ultra-wide, and utilizing gaming mice to up your game.

This week we give away Joe's stuff, we break up with IE8 like a big boy, Joe and Allen get excited about readme files, and we argue about which is worse: bad code or bad architecture. That and more in this week's episode where we explore the new bits in ASP.NET 5.

This week we tackle one of life's great quesitons, does Jack Bauer give high fives? Also, we go over everything you need to know about delegates, events, callbacks and closures in .NET.

Big thanks to <a href="http://twitter.com/kappelcodesalot">@kappelcodesalot</a> for being the inspiration for this episode!

Talking about how to best organize your code, moving from school-work to work-work, the future of Silverlight, and (as always) lots of poo-pooing.