4 ms·
Postgres is neither cattle, nor are there “instances”, because it assumes full responsibility for the data it manages. For example you can not have 2 postgres
by eska 4y ago
Postgres is neither cattle, nor are there “instances”, because it assumes full responsibility for the data it manages.
For example you can not have 2 postgres instances, each with their own locking mechanisms, check whether transactions are serializable, since they don’t know about the locks in the other instance.
This is very basic stuff so I wonder whether people who argue for treating databases like web servers lack basic training in this area.
- motoboi 4y agoYeah, right? You'd be amazed about what people can achieve with bash scripts and kubernetes containers. The crux of my argument is: you probably don't need postgres in kubernetes on the cloud (just use the damn cloud api to manage your database), but if for any reason you want to, manage a postgres with kubernetes it's like managing it with systemd. Way more involved, but doable. Great part is: just as vast majority of people don't write their own systemd units or postgres management scripts, they can use kubernetes operators and benefit from the open source knowledge and ecosystem.