Learnings and future decisions

We haven’t really broken anything here, so the question is how much was there to learn? Well, a lot! We can deploy a production solution without using a million different technologies and with minimum complexity.

Specifically, what we’ve learned is that designing and deploying a solution is a very pragmatic but not very complex approach. Abstracting away the requirements from a use case and visualizing those requirements is very helpful.

There’s also a cause for concern. Imagine, in this scenario, that we are a start-up; we don’t really want to spend 100% of our time automating everything. We need to add value to the business and we need to do that quickly. ACA really helps us with that as it abstracts away a lot of the complexity that Kubernetes brings. But, as we’ve seen in the passing of environment variables, some things are not that flexible. Take the default hostname for example https://customer-a-api.internal...