Trap or integrated win-win?
We use one of these "aggressively simple" architectures too. At this point, I would quit my job instantaneously if I had to even look at k8s or whatever the cool kids are using these days.
We use one of these "aggressively simple" architectures too. At this point, I would quit my job instantaneously if I had to even look at k8s or whatever the cool kids are using these days.
I'm fine with complex architecture and would actually welcome someone choosing something complex but the issue is that we have perverse incentives at work to introduce stuff just to pad our resume.
Kubernetes was designed for companies deploying thousands of small APIs/applications where management is a burden. I've seen companies that deploy 3 APIs running Kubernetes and having issues...
Not a yaml document in sight.
Puppet? Luxury. I started my configuration management journey with cfengine. And the folks that I first heard CM about started with Makefiles:
* http://www.infrastructures.org/papers/bootstrap/bootstrap.ht...
* https://www.usenix.org/legacy/publications/library/proceedin...
That output is 100% of what you need to run our entire product stack on a blank vm.
Monolithic pays for itself in so many ways. Sqlite and other in-process database solutions are a major factor in our strategy.