Have you struggled with increasing complexity of managing and maintaining software configuration? Some time ago, I saw a reference to what was called the Configuration Complexity Clock. It describes phases in how the complexity of software configuration grows. This name originally came from a blog post by Mike Hadlow in 2012.
This is something we should know and think about before we end up in a bad, unmaintainable place.
Do you have a love/hate relationship with YAML or JSON for configurations?
Are your configurations getting messed up because of simple typos, or problems with white space, or confusion between strings and numbers?
Do you try to manage some templating solution on top of YAML?
Is it hard to manage complex overrides across multiple configuration files?
If any of these questions resonate with you, then this article may interest you!
Have you sometimes been frustrated over some feature which you can do via AWS Console, or perhaps via AWS CLI or one of the AWS SDKs (Software development Kits), but…
Setting up infrastructure through ClickOps, even if we may not admit to it, is often a reality. ClickOps is setting up infrastructure through the web interface of the cloud provider,…
Pulumi is a player in the infrastructure-as-software space that I find really interesting. One of the tools they provide is the Pulumi Service, which is a management platform for the…