API World + Integrate 2016

It's about time we started taking configuration seriously. We've all done it: application configuration scatter-gunned over environment variables, varying file formats on disk, bespoke look-up database tables, and if you're stuck doing the corporate time-warp again through no fault of your own, registry entries. Gnarly enough when it's just you and your dev machine, positively Groot across your testing, staging, and distributed live environments. Deployments and ops are hard enough to get right without the extra variables surrounding your configuration thrown in the mix between deployment scripts. A lot of the time, config is too complicated to fit easily into a bunch of environment variables.

How can we make this better? We've been thinking about the concept of Configuration-as-a-Service, and how it can make your custom application configuration easy and secure. It encapsulates configuration management for your mutable business data, technical configuration settings and sensitive data such as keys & credentials. As a design pattern, it helps you architect your solution cleanly by separating configurable business logic, data and technical information from both your code, and from your infrastructure. Join us for a look at how you can use Configuration-as-a-Service to allow developers and admins to manage securely the full life-cycle of your bespoke application configuration from the cradle to the grave in highly distributed environments.