undefined | Better HN

0 pointsjmillikin4y ago0 comments

It honestly sounds like you've confused Kubernetes with some other platform.

Running a big Java monolith with 128GiB RAM footprint in Kubernetes works well. It's at its best when deployments are infrequent and traffic patterns are stable (or at least predictable).

If someone wants stateless microservices with immediate scale-up/scale-down, then that's more like a FaaS ("functions as a service") and they'll be better off with OpenFaaS instead of Kubernetes.

0 comments

1 comments · 1 top-level

rtpg4y ago

The true happy path: you have a big monolith hungry for resources, several instances of the monolith, and you want to be able to relatively quickly spin up new instances (modulo provisioning new nodes) without having to jump through 100 hoops.

For all people talk about autoscaling and whatnot, just hitting some buttons/sending a couple commands manually and getting some temporary scaling for reason X (or a temporary container for reason Y) without messing with a bunch of admin consoles is very nice.

j / k navigate · click thread line to collapse