Container technologies at Coinbase: Why Kubernetes is not part of our stack (blog.coinbase.com)

Article summary

The article discusses Coinbase's decision not to use Kubernetes in their stack, but the text of the article is not available. The comments reveal that the article likely discusses the challenges and complexities of using Kubernetes. Some commenters agree that Kubernetes can be overly complex, while others defend its use. The discussion also touches on alternative container orchestration tools like Nomad and Mesos.

Main themes

• Kubernetes complexity
• Alternative container orchestration tools
• Container orchestration challenges
• Scalability and management
• Proprietary vs open-source solutions
• Company-specific needs and requirements

What commenters say

• Kubernetes is too complex and has killed other container orchestration solutions.
• Nomad is a viable alternative to Kubernetes, offering a more straightforward design and easier management.
• The complexity of Kubernetes is a necessary trade-off for its functionality and scalability.
• Mesos is still a valid option, but its community support has dwindled due to the rise of Kubernetes.
• Some companies prefer to use proprietary solutions like AWS ECS instead of open-source options like Kubernetes.
• The choice of container orchestration tool depends on the specific needs and requirements of the company.
• Kubernetes' lack of built-in user authentication and other features can make it difficult to manage and secure.
• Alternative tools like Nomad and Consul can provide a more streamlined and efficient container orchestration experience.