Blog
Business
Heroku
4
minutes

Qovery and the Twelve-Factor App methodology

The Twelve-Factor App methodology is a methodology for building platform-agnostic and resilient applications. It was introduced by Adam Wiggins while working at Heroku in 2011. Nearly 10 years later, this methodology is still considered by the developer community as an excellent practice to follow when building an application. In this article, we will see step by step how Qovery's DevOps automation software respects and improves the 12-factor methodology. Here we go.
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

Codebase

One codebase tracked in revision control, many deploys.

Qovery integrates seamlessly with Git to deploy branch-based applications. Qovery follows the GitOps methodology, which refers to 1 branch = 1 isolated environment. Each modified environment (production, staging, development) does not impact the others. Plus, Qovery brings a consolidated view of all applications and services (databases, brokers) running within an environment. Developers get the complete picture of their applications and can be confident in their changes into production.

Dependencies

Explicitly declare and isolate dependencies.

Qovery lets you declare all the dependencies that your application needs (databases, brokers, routing, domains...) using a .qovery.yml file and a Dockerfile. Nothing more to go into production. Qovery interprets these files, builds the application, provides the infrastructure, deploys it, and makes sure everything works. In case of any problem, Qovery rollback the application and the dependencies into the last desired states, and the developer is informed by a notification.

Config

Store config in the environment.

Qovery's obsession is to simplify application deployment in the Cloud for all developers. Qovery manages all parameters (URL, URI, port, username, password...) as environment variables. Each environment variable is transparently injected at the start of your applications. No other dependency is necessary to access the services (databases, brokers). Qovery even manages your .env (dotenv file) natively. Simple and powerful.

Backing services

Treat backing services as attached resources.

Qovery manages a set of applications and services (databases, brokers...) as a single application within an "environment". Each environment is isolated from the other. This allows excellent agility to work in teams without stepping on each other.

Build, release, run

Strictly separate build and run stages

From build to run, Qovery sets the pace - either by providing everything you need (CI, CD) or by connecting to your own existing services. Everything is utterly configurable to your needs.

Processes

Execute the app as one or more stateless processes

Qovery seamlessly manages stateless (containers) and stateful (databases, brokers...) applications. For stateful applications, Qovery provides the necessary resources (disk, RAM, CPU) and manages them over time (backup, restore) according to the developer's usage. Everything is done to make it evident for the developers and manageable for the administrators.

Port binding

Export services via port binding

The means of communication between applications in Qovery is TCP/UDP from inside and HTTP from outside. The only thing the developer has to specify is the listening port of his application using the EXPOSE directive in his Dockerfile. Which he already does!

Concurrency

Scale-out via the process model

Qovery manages the automatic scaling of applications and services. Everything is transparent by the developer but configurable by the SRE teams can configure the granularity of the scaling.

Disposability

Maximize robustness with fast startup and graceful shutdown

Qovery allows anyone to start and stop a complete application (multi-services) quickly, thanks to the Environment concept. Creating an environment can also be ephemeral by reacting to some events (Eg. Pull Request) - Eg. Useful to make end-to-end tests. The flexibility of the Cloud is really within reach of everyone.

Dev/prod parity

Keep development, staging, and production as similar as possible.

Using Qovery guarantees that your development, staging, and production environment are all three identical. Even data may or may not be automatically copied from one environment to another - the choice is yours. What better way to develop new features without surprises?

Logs

Treat logs as event streams.

Qovery centralizes access to your application logs. In one command (qovery log), you will have all the information about your applications from your environment. Moreover, without any difficulties, Qovery integrates perfectly with solutions such as Datadog and Sentry and any other Docker compatible solution.

Admin processes

Run admin/management tasks as one-off processes

Qovery provides all the tools necessary for a team of administrators to modify all the settings. Need to restart a service? Need to roll back a service? Prevent the deployment of new releases? Or even to define rights? No problem, it's possible with the Qovery interface.

Wrapping up

This article shows that the Twelve-Factor App methodology is an excellent starting point to design an agnostic, resilient, and scalable application. Even though Heroku initially created this methodology, we have seen that Qovery is fully compliant with it and goes beyond it by offering improvements such as managing multiple applications within a single environment.

Do you use Heroku? Contact us to discover how Qovery can help you take your business to the next level while reducing your infrastructure and R&D costs.

Share on :
Twitter icon
linkedin icon
Ready to rethink the way you do DevOps?
Qovery is a DevOps automation platform that enables organizations to deliver faster and focus on creating great products.
Book a demo

Suggested articles

Product
Observability
5
 minutes
Alerting with guided troubleshooting in Qovery Observe

Get alerted and fix issues with full context. Qovery Observe notifies you when something goes wrong and guides you straight to the metrics and signals that explain why, all in one place.

Alessandro Carrano
Head of Product
DevOps
Developer Experience
 minutes
Top 10 Terraform Cloud Alternatives: The DevOps Guide to Escaping "State File Nightmares"

Tired of rising licensing costs and complex state management? Discover the top 10 alternatives to modernize your Infrastructure as Code, empower developers, and regain control of your cloud spend.

Mélanie Dallé
Senior Marketing Manager
DevOps
 minutes
Top 10 Jenkins Alternatives: The DevOps Guide to Escaping "Plugin Chaos"

Tired of Jenkins maintenance and broken pipelines? Discover the top 10 alternatives to modernize your CI/CD, automate environments, and reduce operational toil.

Mélanie Dallé
Senior Marketing Manager
DevOps
 minutes
10 DigitalOcean Alternatives for Scaling DevOps Teams

Top DigitalOcean alternatives for scaling teams. Compare Qovery (Multi-cloud automation), AWS, GCP, and Vultr to find the best fit for performance and scale.

Mélanie Dallé
Senior Marketing Manager
DevOps
 minutes
Top 5 Vercel Alternatives: Escape Cost, Lock-in, and Frontend Constraints

Stop paying Vercel overages and battling lock-in. Compare Qovery (full-stack automation on your cloud), Render, Netlify, and Fly.io to find the best alternative for DevOps and enterprise scaling.

Mélanie Dallé
Senior Marketing Manager
DevOps
 minutes
Top 8 OrbStack Alternatives: Choosing the Right Tool for DevOps & Production Parity

Top OrbStack alternatives for developers and teams. Compare Qovery, Rancher Desktop, Podman, and Colima to find the best tool for performance, cross-platform stability, and K8s integration.

Mélanie Dallé
Senior Marketing Manager
Heroku
AWS
Cloud Migration
13
 minutes
How to Migrate from Heroku to AWS: A Strategic Blueprint for Mid-Market Teams

Outgrowing Heroku? Stop the manual DevOps grind. Migrate to AWS in <7 days using AI to generate Terraform, EKS configs, and a seamless developer experience.

Mélanie Dallé
Senior Marketing Manager
DevOps
Platform Engineering
9
 minutes
10 Best CI/CD Platforms for DevOps Teams: Automate Pipelines at Scale

Stop managing complex YAML and plugin hell. Compare the top 10 CI/CD platforms for DevOps, from Jenkins to Qovery, and learn how to build high-velocity, automated pipelines on your own cloud.

Morgan Perry
Co-founder

It’s time to rethink
the way you do DevOps

Turn DevOps into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.