my 'simple vs complex' post touched some nerves. it shld have. if you’re starting w/ assumption ‘we need containers’, everything looks like an orch issue. why do you need containers? first principles, folks - me a short while ago on the twitr machine Why Do You Need Containers? Let’s cut right to the point: if you can’t clearly answer that question in one or two sentences, you don’t need containers.
You may have walked away from my last post with the impression that I don’t want to use containers. Today’s post addresses that - Containers increase developer productivity & reduce or eliminate environment drift through the release promotion cycle That’s not meant to sound like consultant doubletalk, but it does. Here’s what I mean: Speed & Agility When a dev team takes the upfront time to settle on a single toolchain & set of supporting processes, this can often (always?
I just read another post (which read as a thinly disquised advertisement) discussing how great kubernetes (k8s) is, even though it’s difficult to implement and virtually impossible to use without a ton of custom development, and probably even then a consultancy should be engaged to get it right. Umm… isn’t a framework supposed to reduce complexity? Let’s get some disclosures out of the way: I’ve met all & socialized with one of the original k8s authors.