News Update


12 Factor Microservices Architecture

The Roadmap to Scalable and Resilient Applications 

In the realm of software development, the 12 factor app methodology has surfaced as a guiding beacon for building scalable, resilient, and manageable applications. When applied to microservices architectures—self contained services that work collectively as part of a larger system—these principles transform into the blueprint for success in today's dynamic digital ecosystem.

 1. Codebase 
A single codebase tracked in version control, with many deployments, is the bedrock. For microservices, each service has its codebase, ensuring that every microservice is independently deployable, upgradeable, and maintainable.

 2. Dependencies 
Explicitly declare and isolate dependencies. Microservices encapsulate their specific dependencies, eliminating the risk of version conflicts and easing the path for continuous deployment.

 3. Configurations 
Store configurations in the environment. This separation of config from code means that the same microservice can run in different environments, from local development to production, without changes.

 4. Backing Services 
Treat backing services as attached resources. Microservices interact with databases, message queues, and other services through URLs and other credentials stored in the configuration.

 5. Build, Release, Run 
Strictly separate build and run stages. By doing this, microservices ensure that any change that needs to be made is created as a new release, reinforcing stability and control.

 6. Processes 
Execute the app as one or more stateless processes. Microservices do not retain state between requests; instead, they store data in a stateful backing service, which promotes scalability and resilience.

 7. Port Binding 
Export services via port binding. Microservices communicate with each other through well defined APIs over the network, offering flexibility in service deployment and scaling.

 8. Concurrency 
Scale out via the process model. Leveraging the cloud's ability to start and stop processes rapidly, microservices can be scaled in or out quickly, adapting to load changes without disrupting the system.

 9. Disposability 
Maximize robustness with fast startup and graceful shutdown. Microservices are designed to be started and stopped at a moment's notice, which makes continuous deployment and resilience to system crashes a reality.

 10. Dev/prod parity 
Keep development, staging, and production as similar as possible. With microservices, developers work in environments that closely mimic production, significantly reducing the chances of "but it worked in dev" issues.

 11. Logs 
Treat logs as event streams. Microservices do not concern themselves with routing or storage of their output stream; they treat logs as a continuous flow to be captured and handled externally.

 12. Admin Processes 
Run admin/management tasks as one off processes. This ensures that any admin tasks (migrations, database cleanup, etc.) are kept separate from the application's main processes, allowing for better maintenance and less complexity.

The 12 factor methodology offers an efficient pathway for organizations to develop microservices that are both scalable and operationally sustainable. By following these principles, developers and companies can build systems that are not only resilient to the ever changing technological landscape but are also poised to thrive within it.

"Talent is a gift, but learning is a skill. Embrace the journey of growth."