3 ms·
(2016) 2017 Followup: https://patrobinson.github.io/2017/12/16/should-i-run-a-database-in-kubernetes/ https://patrobinson.github.io/2017/12/16/should-i-run-a-d
by phnofive 6y ago
(2016)
2017 Followup: https://patrobinson.github.io/2017/12/16/should-i-run-a-database-in-kubernetes/ https://patrobinson.github.io/2017/12/16/should-i-run-a-data...
Tone softens a bit, but still comes to the conclusion it’s not a good fit. Four years on, I can’t imagine a benefit to running a prod DB out of a container either.
- ghshephard 6y agoThe advantage is you deploy your entire application stack the same way you would anything else. Zero effort to roll out new environment. And if you need to scale it up, you just increase your k8s request/limit on CPU/Memory and restart it and it gets scheduled to a node as appropriate.
- knowhy 6y agoI don't see the benefit either. I believe Netflix made this idea popular with sidecar containers as a way to add > “non-intrusive platform capabilities” [0] to container stacks. I understand that the idea might be popular among developers as it is easier to just add a database container to your stack rather than dealing with the db admin. I don't know if Netflix ever recommended databases as sidecar containers. But I have seen it in the wild where dev followed the Netflix model. I sometimes hear people arguing that they have to manage containers anyway so it would be less overhead to manage the db as a container as well. 0: https://netflixtechblog.com/prana-a-sidecar-for-your-netflix-paas-based-applications-and-services-258a5790a015 https://netflixtechblog.com/prana-a-sidecar-for-your-netflix...