
Twelve-Factor App | Treat Logs as Event Streams
The eleventh factor of the Twelve-Factor App methodology emphasizes treating logs as event streams.

The eleventh factor of the Twelve-Factor App methodology emphasizes treating logs as event streams.

The tenth factor of the Twelve-Factor App methodology emphasizes keeping these environments as similar as possible.

The ninth factor of the Twelve-Factor App methodology emphasizes disposability.

The eighth factor of the Twelve-Factor App methodology emphasizes scaling out via the process model.

The seventh factor of the Twelve-Factor App methodology emphasizes exporting services via port binding.

The sixth factor of the Twelve-Factor App methodology emphasizes executing the app as one or more stateless processes.

The fifth factor of the Twelve-Factor App methodology emphasizes the strict separation of these stages.

The fourth factor of the Twelve-Factor App methodology emphasizes treating backing services as attached resources.

The third factor of the Twelve-Factor App methodology emphasizes storing configurations in the environment, rather than in the 3code.

The twelfth factor of the Twelve-Factor App methodology emphasizes running these tasks as one-off processes.

The second factor of the Twelve-Factor App methodology highlights the importance of explicitly declaring and isolating these dependencies.

The first factor of the Twelve-Factor App methodology emphasizes the importance of having one codebase tracked in revision control, with many deploys.