12 Factor - RJStanford

Sign in Subscribe

12 Factor

In this series I will explore my thoughts on the 12 Factor principles for SaaS development, where I diverge from them (and why), and how they can help you build clean, scalable software.

Disposability

Normalize not knowing where - or to some extent why - your processes are. And never, ever, name a server (sorry saruman37)

Concurrency

Sometimes its okay to be a monolith. Or at least one monolith amongst many.

Port Binding

Making sure that you have a single, simple, well-understood entry point to your service.

Processes

State belongs in clients and database, nowhere in between.

Build, Release, Run

Build, Release, Run

> Strictly separate build and run stages What problem are we solving? Builds should be repeatable, trivial, and boring. If you can build your application twice in a row on different servers and get different results than you have a problem. Additionally, the build should be hands-off. If your build

Backing Services

Backing Services

How should you incorporate 3rd party services, and their configurations, into your SaaS app? Are they just another dependency or something more?

Config

How and where should you be storing runtime configuration, especially secrets?

Dependencies

How and where do you define, update, and import your dependencies?

Codebase

How many codebases make up a deployable? How many deployable can you build from one codebase?

12 Factor Applications

12 Factor Applications

The 12 Factor “manifesto” was written by Adam Wiggins back in 2012 and has become something of a template for building scalable, modern applications in the RESTful era. Find out how it can help you write simple, scalable software for the modern age.