The last 10 years, I managed 700 database Clusters. Anything from a few megs to terrabyte database sizes.
The main issues are:
huge pages. They work an bare metal, not so much in kubernetes ( I am not talking about transparent huge pages…)
Core/cache locality.
NUMA
And of course: maintainability. Especially in the PIT recovery.
Zalando has an open source operator + patroni bases images. They work for many cases, and are a great way if you can’t manage postgresql on bare metal.
And of course: if you have everything running on k8s, running a few bare metal servers for a db is a pain in the ass, and in such cases it is if course better to just deploy an operator in your cluster and let it handle the heavy lifting like backup and replication.
No, because of many factors:
The last 10 years, I managed 700 database Clusters. Anything from a few megs to terrabyte database sizes.
The main issues are:
And of course: maintainability. Especially in the PIT recovery.
Zalando has an open source operator + patroni bases images. They work for many cases, and are a great way if you can’t manage postgresql on bare metal.
And of course: if you have everything running on k8s, running a few bare metal servers for a db is a pain in the ass, and in such cases it is if course better to just deploy an operator in your cluster and let it handle the heavy lifting like backup and replication.