Hacker News new | past | comments | ask | show | jobs | submit login

Are there good resources for making that decision according to good criteria?



A simple rule of thumb is the number of services you have. For instance, my current employer has been working on getting everything on Kubernetes for the last year or so and we have two services... the frontend server-side renderer, and API.


/snark So is that a cluster per app or a namespace per app?


The criteria is basically: do you have the time, people, expertise and willingness to build a custom dev platform on top of Kubernetes?

If yes, Kubernetes might make sense for you, if your company is large enough that a PaaS like Heroku is prohibitively expensive.

If no, you don't want Kubernetes.

https://twitter.com/kelseyhightower/status/93525292372179353...




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: