It depends upon what your startup is doing. Maybe Kubernetes is overkill for a basic "CRUD" web app backed by a relational database and some object storage. It

It depends upon what your startup is doing. Maybe Kubernetes is overkill for a basic "CRUD" web app backed by a relational database and some object storage. It's very helpful at our business that runs a variety of web services that are powered by batch data workflows. Kubernetes enables us to spread both the process workloads and the batch workloads across sets of servers, with redundancy. For others in a similar situation, I'd highly recommend the combo of Kubernetes and Argo Workflows. We wrote a blog post about one of our workflows at https://www.interline.io/blog/scaling-openstreetmap-data-workflows/ https://www.interline.io/blog/scaling-openstreetmap-data-wor...