11–20 of 61 posts
I'd say 99% of companies using Kubernetes can't really explain why they chose it over Nomad.
The entire reason is popularity/marketshare, and that's a really valid reason to choose tech like this.
There is a corollary to this: Do you really need cloud infrastructure? Cattle not pets right? Well, no. Have you seen amazons AWS margins? Its 30%. After amazon buys hardware, pays people to run it, it still makes 30%. Not having hardware is someone else's profit. That isnt cattle, its contract poultry farming. Learn capacity planing. Learn to write cachable, scalable apps. Track your hardware spend per customer. Lea…
I'm expected to write a service like s3?
That said, we are planning on doing a cloud exit in the future. I don't feel we need Kubernetes, but we do need to orchestrate containers. In our case, it's less scale, and more isolation.
The simplest thing you could do is to build a single-container application, and deploy it a Heroku-like system with a fully managed database. If this actually works for your use case, then definitely avoid Kubernetes.
But eventually you'll reach a point where you need to run a dozen different things, spread out across a bunch of servers. You'll need cron jobs and Grafana and maybe some centralized way to manage secrets. You'll need a bunch of other things. At this point, a managed Kuberentes cluster is no worse than any other option. It's lighter weight than 50 pages of Terraform. You won't need to worry about how to get customized init scripts into an autoscaling group.
The price is that you'll need to read an O'Reily book, you'll need to write a moderate amount of YAML, and you'll need to pay attention to the signs reading Here There Be Dragons.
Kuberentes isn't the only way to tackle problems at this scale. But I've used Terraform and ECS and Chef and even a custom RPM package repo. And none of these approaches were signficantly simpler than Kubernetes once you deployed a full, working system for a medium-sized organization.
Related: https://doineedkubernetes.com/
There is a corollary to this: Do you really need cloud infrastructure? Cattle not pets right? Well, no. Have you seen amazons AWS margins? Its 30%. After amazon buys hardware, pays people to run it, it still makes 30%. Not having hardware is someone else's profit. That isnt cattle, its contract poultry farming. Learn capacity planing. Learn to write cachable, scalable apps. Track your hardware spend per customer. Lea…
There is a corollary to this: Do you really need cloud infrastructure? Cattle not pets right? Well, no. Have you seen amazons AWS margins? Its 30%. After amazon buys hardware, pays people to run it, it still makes 30%. Not having hardware is someone else's profit. That isnt cattle, its contract poultry farming. Learn capacity planing. Learn to write cachable, scalable apps. Track your hardware spend per customer. Lea…
> Not having hardware is someone else's profit. But it's also someone else's economies of scale. The chances of me getting datacenter space, hardware, bandwidth, and expert 24/7 staffing at the same volume discounts they do is... slim. Particularly for the small amounts I'd need.