dev/prod parity
Keeping development, staging and production as similar as possible in timing, people and tools.
In more detail
Factor X of the twelve-factor app names three gaps: the time gap between writing and running a change, which should be hours; the personnel gap between authors and operators, which should be zero; and the tools gap between backing services, which engineers create themselves with a lightweight local database. The bugs that survive testing are the environment-specific ones.
Related terms
- staging — A pre-production environment set up like production, where changes are tried out before they reach real users.
- backing service — Any service an application uses over the network, such as a database, cache, queue, mail relay or payments provider.
- SQLite — A small relational database that runs as a library inside your program and keeps the whole database in one file.
- works on my machine — The classic complaint when software runs for one developer but fails elsewhere because of hidden differences between machines.
Taught in
- Disposability, Dev Prod Parity And Logs — DevOps & Site Reliability Engineering