Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It makes redundancy, self healing, scaling, rolling updates, rollbacks and the like error easy, assuming that your services are stateless.

If you do not need this features k8s is not the thing to use, unless you have the skill set anyways.

Things get messy when state and persistence is involved, I’d prefer to habe my backend DB not on k8s and link the services against it.



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

Search: