1 What Is the Twelve-Factor App Methodology?
While not strictly a set of architectural principles, the Twelve-Factor App methodology is a set of best practices for cloud-native applications.
2 How Does the Mendix Runtime Support Twelve-Factor Cloud-Native Apps?
The sections below describe how Mendix conforms to the Twelve-Factor App methodological requirements.
By default, the source code for every application you create with Mendix is stored in the Mendix Team Server code repository. When you deploy an app, a package is created based on your model as stored in the Team Server. This package is then deployed to your different environments, for example acceptance or production.
All the dependencies (like modules and libraries) used by your app’s modules are part of the app model. This means that no implicit dependencies to tools exist in your environment. This ensures reliable deployments.
Configuration needs are defined in your application model through constants. These values can be specified at deployment time in your environment, or through APIs called in your CI/CD pipeline. The actual configuration values are never part of your model, which means that the same deployment package can be deployed in any environment without changing the app model.
1.4 Backing Services
All external requirements (like the database to store your application data) and services to be called from your application can be configured at deployment time. Like the previous requirements, this ensures that the same tested deployment package can be used in any situation, with any backing service, without model changes.
1.5 Build, Release, Run
If it was possible to change code in a production environment, the scaling of your application would become unpredictable and unreliable. It would also make debugging and problem-solving harder. To avoid this problem, the Mendix Platform clearly separates the build and run stages.
In the Mendix Developer Portal, you first have to build a package from your model, which can then be deployed to your environments. If you want to make a code change in production, you have to modify your model then build a new package. Mendix also provides APIs to build and deploy your applications, so you can incorporate this approach in your custom CI/CD pipeline.
The Mendix Runtime is designed to be completely stateless. It shares data through a database, ensuring easy scalability and resilience.
1.7 Port Binding
To ease the scaling and running of the same app in different environments, the app should be self-contained (meaning, where it listens for client requests should be configurable). Mendix apps can be configured in this way, enabling the underlying platform-as-a-service (PaaS)—for example, Cloud Foundry—to easily scale the number of containers hosting your app.
Mendix uses a combination of Java threads and processes to scale to the demand of your end-users. The Twelve-Factor App methodology stresses the need to scale via processes; otherwise, you will be limited in your scaling requirements to the maximum of what one Java virtual machine (JVM) can support (vertical scaling). By also supporting process scaling, extra resources can always easily be added (horizontal scaling).
Mendix Runtime instances can be stopped and started as required. In a multi-instance environment, users will usually not notice if one runtime instance is restarted. The benefit of this is that horizontal scalability is simpler and faster, and deployment of new versions or new configuration becomes faster.
1.10 Development/Production Parity
To guarantee quality, apps deployed in testing environments should behave similarly in production environments. In the Mendix Cloud, all environments are provisioned in the same way. The only differences are configuration, data, and your application. Data can be moved between environments through backup and restore to ensure testing with representative data.
Mendix Cloud uses the Cloud Foundry firehose to collect all the log events from all your applications. This can be viewed and filtered in the Mendix Developer Portal.
1.12 Admin Processes
To avoid synchronization issues, the Twelve-Factor App methodology advises shipping administrative code with application code. Mendix enforces this practice, so the only code that will run in your app environment is code that is part of your app. This means that you need to make admin code part of the model. Users often implement this with admin logic in an admin page by either implementing a microflow to run after the app has started or creating APIs to trigger admin actions.