4 ms·
We self-host a postgres cluster in k8s (AKS). The main reason being that the Azure postgres offering was not fit for (our) purpose. We did start with the Azur
by thrixton 5y ago
We self-host a postgres cluster in k8s (AKS).
The main reason being that the Azure postgres offering was not fit for (our) purpose.
We did start with the Azure offering, and our default is generally to use the cloud offering.
- ajax33 5y agoCould you please elaborate on what the drawbacks with the Azure postgres offering are? I am currently evaluating the same choice - Azure Postgres vs self-hosting in my k8s cluster.
- mthomassen 5y agoNot parent, but at {work} we made a similar move, from Azure managed postgres to self-managed postgres. I elaborated a litle on why here: https://news.ycombinator.com/item?id=24607664 https://news.ycombinator.com/item?id=24607664 but boils down to; - enormous performance difference - advanced/fine grained user roles (+default permissions, not settable without superuser) - use of extensions (productivity boosts for us come from; Oracle FDW, TDS FDS, TimescaleDB) - private network endpoints - lower cost
- xiwenc 5y agoI’m also interested. We are currently using the managed pg server where we create multiple databases inside. The managed pg database does not support private endpoint if i recall and it gets pretty expensive. Also single managed server doesn’t scale well.