3 ms·
First question: why you need many containers for just 3000 users? That should easily run on a cheap VPS unless you're doing something ridiculously complex. Why
by capableweb 4y ago
First question: why you need many containers for just 3000 users? That should easily run on a cheap VPS unless you're doing something ridiculously complex.
Why target any cloud APIs at all if your product have a small amount of users? You don't need to scale up/down fast at if you're just at 3000 users. Throw it on a Linux box, write a systemd service and be done with it.
- mountainriver 4y agoI'm not talking about 3k users, he said 99% of use cases
- capableweb 4y ago> 99% of companies Most companies have small amount of users and don't have rapidly shrinking/growing user bases, meaning their infrastructure need is not rapidly shrinking/growing neither, in most cases. Hence, Kubernetes being accidental complexity most people can do without, rather than necessary complexity.
- mountainriver 4y agoEh I don't have the numbers, but every company I've worked for has had lots of users. Their infra wasn't shrinking or growing much to make good use of k8s. Mainly they needed to link a bunch of runtime containers together built by different teams. I get why people say k8s is complex, but there really isn't another great option for running a containerized service based architecture, maybe nomad