In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service.
The twelve-factor app is a methodology for building software-as-a-service apps that:
- Use declarative formats for setup automation, to minimize time and cost for new developers joining the project.
- Have a clean contract with the underlying operating system, offering maximum portability between execution environments.
- Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration.
- Minimize divergence between development and production, enabling continuous deployment for maximum agility.
- And can scale up without significant changes to tooling, architecture, or development practices.
The twelve-factor methodology can be applied to apps written in any programming language, and which use any combination of backing services (database, queue, memory cache, etc).
One of those twelve-factors describes the best way to manage app configuration. One of the requirements listed there is “strict separation of config form code”. Config varies substantially across deploys, code does not.
Ajustee allows to move settings from codebase to a secure cloud storage with lot of extra functionality. That approach allows you to share your code without a risk of compromising some credentials. You can easily manage settings using Ajustee console between deployments, change configuration values on a run, partially replace config values for subset of users or use cases.
Ajustee uses HTTP REST API that can be accessed using any language from any platform. On top of REST API Ajustee has several SDKs in your languages that wraps REST API calls into language-friendly modules.
This article was first published on Medium
ajustee.Medium
Visit Ajustee Blog for more articles on how to manage configuration.
Top comments (0)