Tag: 12-factor

We should run background jobs as one-off processes to scale them independently and ensure they have the correct resources assigned to them.

We should run background jobs as one-off processes to scale them independently and ensure they have the correct resources assigned to them.

Capture and process those logs centrally using an observability stack; which means we can set up monitoring and alerting.

We should have parity between instances run in local development and those run in the production environment so that we run into fewer issues

The seventh factor in a 12-factor app is that the app should “scale out via the process model.” Concurrent processing helps us scale out our application by performing processing in parallel.

The seventh factor in a 12-factor app is that the app should “scale out via the process model.” Concurrent processing helps us scale out our application by performing processing in parallel.

The sixth factor in a 12-factor app is that the app should “export services via port binding.” Port binding improves an application’s portability and security and makes it easier to work with by allowing us to have multiple processes that each have their own port on which they communicate.

Does your web server keep running out of resources? Achieve scalability by making your apps stateless for better reliability, faster rollback & independent scaling of processing and storage for a more cost-effective hosting solution.

Harness the power of scalability by separating build, release & run stages of your deployment pipeline for better reliability, faster rollback & independent scaling of processing and storage for a more cost-effective hosting solution.

A 12-factor app does not store config in the codebase. Here’s what to do instead.