Every now and then I come across blog posts with titles like:

• Kubernetes is on its way out: DevOps teams are using xyz instead
• Company x ditched Kubernetes: Here's what they are using right now
• Why Kubernetes is slowly dying

These blog posts have one thing common.

They take one or more cases where Kubernetes is not a good fit (or not required). Then they build a myth around this case and claim that since Kubernetes is not a good fit (or not required) for this specific case, Kubernetes is not good for anything and so is on its way out.

Every engineer knows that logic is wrong.

Still these myths are quite compelling.

Myth #1: The monolith is back

This myth says that DevOps teams are abandoning microservices and returning to monolithic architecture.

This is a BIG, BIG mythical story. What's the truth?

The monolith never went away.

Both monolithic and microservices are valid architectural patterns. Each have pros and cons. Software teams have been using both depending on requirements of the software project.

A monolith can be the right choice for smaller, less complex applications, offering a simpler development and deployment process.

But, as an application grows, a microservices architecture becomes invaluable, allowing for independent development, scaling, and deployment of individual components.

Software teams don't choose one over the other based on fleeting trends; they select the pattern that best fits their specific use case and business requirements. Both architectures will continue to coexist, and so will the need for container orchestration.

Myth #2: PAAS is replacing Kubernetes

Another common myth.

Certain DevOps teams do choose Platform as a Service (PAAS) over Kubernetes. And they have valid reasons for doing so.

PAAS is a powerful platform for running some applications.

PAAS abstracts away much of the underlying infrastructure. It simplifies development and deployment, making it an excellent choice for teams that prioritize ease of use.

But, this convenience comes at a cost: limited control and flexibility.

Kubernetes, on the other hand, provides a lower-level, more granular control over your containerized applications. It's a foundational tool that many PAAS offerings are actually built on top of.

Think of it this way: PAAS is a pre-built house, and Kubernetes is the blueprint and construction crew. You don't replace one with the other; you choose the right tool for the job. PAAS and Kubernetes serve different needs and will continue to be a part of the DevOps landscape.

Myth #3: Alternatives like HashiCorp Nomad are replacing Kubernetes

Indeed HashiCorp Nomad is good for orchestrating legacy applications or containerized applications on Docker.

But replacing Kubernetes with Nomad? No. It was never designed to be a one-to-one replacement for Kubernetes.

Nomad is a simpler, more lightweight orchestrator that is perfect for specific tasks, especially in environments where simplicity is paramount. It's often used for batch processing and in scenarios where a full-fledged Kubernetes cluster would be overkill. It's not a competitor in the sense of one-or-the-other, but rather a complementary tool.

Kubernetes offers a comprehensive ecosystem with extensive features for networking, storage, security, and more.

For large-scale, complex, and highly distributed systems, Kubernetes remains the de facto standard. Nomad is a fantastic tool, but it occupies a different niche.

The Verdict: Kubernetes isn't going anywhere

Despite these myths, Kubernetes continues to solidify its position as a cornerstone of modern cloud-native development.

It's not just a trend; it's a fundamental part of the DevOps toolkit. The skills required to work with Kubernetes are in high demand and are consistently listed as one of the most critical for DevOps engineers.

Don't be fooled by the noise. The industry's reliance on container orchestration is stronger than ever, and Kubernetes is at the heart of it.