News for hackers. Stuff that matters.

A comment on Difference between running Postgres for yourself and for others. Parent comment

Re:Difference between running Postgres for yourself and for ... by pwmtr on Tuesday July 23, 2024 @12:13PM (#41047667)
At another thread in this page, I wrote more about this, but in summary; we also like k8s-based managed Postgres solutions. They are quite useful if you are running Postgres for yourself. In managed Postgres services offered by hyperscalers or companies like Crunchy though, it is not used very commonly.
[ Parent | on HN ]
Re:Difference between running Postgres for yourself and for ... by JohnMakin on Tuesday July 23, 2024 @02:15PM (#41049101)
> it is not used very commonly.

Is this a problem of multi-tenancy in k8s specifically or something else?

[ Parent | on HN ]
Re:Difference between running Postgres for yourself and for ... by pwmtr on Tuesday July 23, 2024 @07:44PM (#41052223)
At k8s, isolation is at the container level, thus properly isolating (for security purposes) system calls is quite difficult. This wouldn't be a concern if you are running Postgres for yourself.

Also for us, one reason was operational simplicity. You can write a control plane for managed Postgres in 20K lines of code, including unit tests. This way, if anything breaks at scale, you can quickly figure out the issue without having to dive into dependencies.

[ Parent | on HN ]
Re:Difference between running Postgres for yourself and for ... by tehlike on Tuesday July 23, 2024 @11:31PM (#41053378)
I always assumed crunchy was using their own operator for their managed offering. Is that not the case?

https://github.com/CrunchyData/postgres-operator

[ Parent | on HN ]
Re:Difference between running Postgres for yourself and for ... by pwmtr on Wednesday July 24, 2024 @04:54AM (#41054974)
They have a Ruby control plane; https://www.crunchydata.com/blog/crunchy-bridges-ruby-backen...
[ Parent | on HN ]