4 ms·
I think we're conflating Kubernetes with containers here. I definitely agree that databases don't benefit from running under containers - they are pet-like (an
by maffydub 4y ago
I think we're conflating Kubernetes with containers here.
I definitely agree that databases don't benefit from running under containers - they are pet-like (and so don't benefit from fast spin up or massive horizontal scaling) and tend to require host-level tuning (which breaks the container abstraction).
What Kubernetes brings is a well-principled orchestration framework that can easily be extended with custom operators for workloads such as databases that need it. (In fairness, he does refer to this in passing at the end.)
- deleted 4y ago[deleted]
- KaiserPro 4y agoEverything is easy if you don't have to handle state. K8s was always really crap for persistent storage. On AWS you can always dump to EFS or the managed lustre (what ever thats called). (which is better than attaching block storage.)
- candiddevmike 4y agoPlease don't use EFS for anything requiring speed, especially writes. It's extremely slow in my experience.
- datatrashfire 4y agoOne of my peeves with fargate is it only supports volumes on EFS.
- KaiserPro 4y agoyeah, metadata performance sucks arse, but it serves a purpose.