Speed is sometimes more important than quality, especially when you’re racing to get an MVP out the door at your startup. I’ve seen small companies build great things off systems best described as duct tape and chewing gum. I’ve also seen others get so bogged down in the details of how their automations are configured that they never ship a single line of code to production.
For an enterprise to be successful, you need a balance. Move too quickly and your brittle systems will fail when they meet the first measures of success. Overengineer a platform and a more nimble competitor will eat your lunch before noon.
Balance is key.
Containerization and Kubernetes
I’m a huge proponent of containerization. It helps to package your applications, provides a level of ephemerality to your ecosystem, and makes redeployment/migration/scaling remarkably easy. With tools like Docker readily available, containerization is accessible to both large enterprise development teams and solo engineers.
The industry standard orchestration tool for containers today is Kubernetes. It manages your containers either on-premise or in the cloud, makes scaling a cinch, helps automate zero-downtime deployments, and speeds time-to-recovery for production issues as well. This all being said, it’s insanely complex and a beast to configure for trivial or early projects.
I’ve been using containerization for years, so I understand the frustration that comes with Kubernetes orchestration and the memes around it being overkill for the early days of a product. But none of this needs to be the case.
I’m building a new tool that makes Kubernetes easy – regardless of where you deploy it. The tool takes the guesswork out of setup and configuration and provides you with an effective and efficient baseline for your application.
From zero to Kubernetes on day one with minimal effort.
Want to learn more? Just follow along as I build in public.
