Updated: Sep 30
SWEAGLE removes configData inhibitors and accelerates your cloud strategy. In the cloud, configData changes rapidly as the number of microservices and containers increase. SWEAGLE provides an agnostic repository to validate, manage and secure the moving parts of all your configData.
Migrating to the cloud is not simply about picking up your static applications and dropping them on cloud provisioned resources. To take full advantage of cloud application platforms, you must reconsider architecture and deployment practices as well.
The Twelve-Factor App is a common methodology and set of best practices for building applications on platform as a service frameworks such as Cloud Foundry and Heroku. One important factor, “config”, dictates that code and config should be stored separately and config data should be delineated by environment. Therefore, when an application is deployed in a test environment it can pick up the correct database connection string and not inadvertently connect to production data. Also, proper debug settings should be set in production, so performance isn’t impacted. As SWEAGLE utilizes a graph-based data model, sub-setting specific data by environment is as easy as creating a sub-folder and including environment specific settings so that any config data generic to all environments would then be inherited. This ensures compliance with another important factor, Dev/prod parity. Which states development, test and production should be kept as similar as possible.
Apps deploy faster and more frequently in the cloud. Usually encapsulated in a container, the deployed elements themselves are disposable – deploy, scratch, and rebuild. Typically, yaml files store all the settings needed to provision an environment. To ensure their integrity, the individual configuration settings need to be tracked, versioned, validated and stored securely. SWEAGLE provides a trusted, secure and validated config data repository, accessible securely at any point in the release pipeline through a robust API. Before making the data config available, the SWEAGLE rules engine can validate the settings to ensure that minimal resources are provisioned, naming conventions are enforced, secrets are encrypted and databases are provisioned in the correct geographical region. Furthermore, fine grain role-based access controls can be applied to the individual key value pairs that make up the yaml file. These controls will allow for greater more widely used common set of provision parameters which will improve adoption of the cloud migration strategy.
SWEAGLE is an easily accessible, flexible, and secure config data repository. It provides config data version control plus, a config validation rules engine … exactly what is needed for migrating applications to the cloud!
Would you like to learn more?