
Sign up to save your podcasts
Or


Start Here
Freebies
Resources
Books
Freebies
Resources
Books
Show notes: https://www.codewithjason.com/rails-with-jason-podcast/adam-hawkins-2/
Preflight Checks
Books
https://www.codewithjason.com/rails-with-jason-podcast/adam-hawkins/
The Flow Framework & Four Types of Work
Books
The 12.1 factor approach prefers locality over fully integrated environments. Doing so promotes fast and independent iterations on discrete services using automated tests to verify correctness. End-to-End issues that may have been identified with a fully integrated environment with dev/prod parity should be pushed downstream in the deployment pipeline in accordance with test pyramid principles. If a regression is identified, then it may quickly addressed by adding tests to the relevant service’s test suite.
Topics Mentioned in the Show
Resources
Books
The 12 factor app states that applications should log to standard out and standard error, thus not concerting themselves with the storage and processing of their log stream. That's a good start point, but we need more than that. The 12.1 factor app does these three things:
Mentioned in Show
Resources
Books
The 12 factor app states that applications should read config from environment variables. It implies separation of code and config. That’s about it, but there’s good bones here. I want something bigger from this factor. Specifically that applications may be deployed to new environments without any code changes. This requires a few additions:
Mentioned in Show
Resources
Books
In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that:
The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).
Resources
Books
From the publisher's feed

3 Listeners