Shpend Kelmendi is a Software Engineer and Cloud Architect at bbv Software Services AG. He leads the Cloud Community. His playground: Azure, DevOps, and cloud architecture. As a Microsoft Certified Trainer (MCT), he shares what he learns and helps others succeed in the cloud.
View all authors
I use Azure DevOps across many customer projects. I really like it. One thing I didn't like is the message added to the beginning of the commit when you closed and merged your PR. You can see it above in the image or in my title. Not so nice to read, right? I agree.
If you haven't seen The Matrix, watch it. It's worth it.
The Matrix is a sci-fi action movie about a hacker named Neo who learns that reality is a simulation run by machines. With Morpheus and Trinity, he struggles to free humans from this illusion. However, he must first make a crucial decision:
Blue pill: comfortable illusion. Red pill: uncomfortable reality.
So what does this have to do with Kubernetes? Picking Kubernetes is the same kind of choice.
| Take the Blue Pill if you think | Take the Red Pill if you think |
|---|---|
| Kubernetes solves all my problems. | Kubernetes is very powerful but adds complexity, which is not necessary for current requirements. Let's start simple. |
| It's the future - all big companies use it. | Big companies have big problems and big teams. Your team with 5 developers has different needs than Google. |
| No vendor lock-in - we stay flexible. | You trade cloud vendor lock-in for Kubernetes ecosystem lock-in. Plus managed k8s still ties you to a provider. |
| We need it to stay competitive. | Competitive advantage comes from solving customer problems, not from adopting the latest technology hype. |
| It scales infinitely. | It can scale, but you need the team, monitoring, and infrastructure to support it. And this is not cheap. |
| DevOps will be so much easier. | DevOps becomes more complex. You need specialized knowledge and significantly more operational overhead. |
Which one do you pick?