[vaidhy]

I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

[shudza]

Which is why kubernetes got adopted - everyone pretends they are Google, having Google problems, when they, in fact, don't.

[theideaofcoffee]

This is a heretical idea in some circles. Utter it and expect to be ostracized. In my case it’s cost a few job offers when I’ve suggested that a few python processes running under supervisor (e.g.) would be more than sufficient. It has its place but that point lies at a stage of development and sophistication far beyond where most cargo-cult users are currently.

[nuker]

This is a heretical idea in *most circles. Same experience with job offers!

[mradek]

I think it’s also probably because it gives people a “predictable” way to do things.

That being said I sometimes ask myself why we can’t constantly think KISS and YAGNI. Like, do we really need this level of abstraction and complexity? I’ve been “working” with k8s and I would probably fail any interview on it because I feel like I’m always googling my way through issues. I don’t even care anymore because I know for my own purposes outside of work, I keep my code and systems stupid simple.

And maybe this sounds cringey to some but I’m happy to write a few scripts on my own to handle deployments without needing to break my software into a thousand pieces. Single responsibility code using a few languages that are best suited for the task at hand (in my case it’s mostly node, elixir, go) that’s easy to break apart and ship separately is so nice. Why can’t we do the same at work?

Oh well, I’ll collect my check 2x a month thanks.

[perfecthjrjth]

Large companies are done with huge k8s clusters. Now every app team and their SRE team rolls out their own k8s cluster. I am not sure whether these companies are solving Google scale problems.

[speed_spread]

Maybe they weren't solving Google-scale problems before but with Kubernetes they sure are now!

[MuffinFlavored]

> For a small company, give me a way to run one container in an autoscable way and we can go from there.

What's the best way you've found to do that?

[rufius]

ECS/Fargate for long lived things. Lambdas for short lived things.

[vaidhy]

+1 for Fargate and Lambda. If you do not like Fargate, you can also run containers in EC2 for a bit more control.

[nuker]

Nah, scaling will be hard. I came to realisation that I don’t want any clusters, let them manage it :)

[kingofheroes]

We used to do this at my current job, but we've recently started transitioning to Kubernetes. There are certainly things I like a lot about it (specifically, the k9s CLI), but I definitely miss the simplicity of ECS/Fargate.

[nuker]

That plus fleet of ec2 for real heavy loads.

[democracy]

Google App Engine https://cloud.google.com/appengine

[jbergens]

Azure is really simple if you use dotnet. Just create an app and then click scale-out (or scale-up).

They of course support docker and k8 also. And Azure functions which are like lambda in AWS.

[owenm]

I really like Azure Container Apps for this. It's a great way to dip into the world of containers.