Interesting write up! Would love to learn more about the ‘why’. The post describes one (that etcd has low usage), but that alone doesn’t seem to be a compelling enough reason to do this.
I don’t know for a fact but I would guess there are multiple reasons and all connected to how complex it is to operate etcd.
1. Most people will need to run 3 nodes of etcd (and can never be an even number), and they have to be set up to replicate data etc
2. IIRC, recovering etcd from a total failure of the cluster is not fun (e.g. if you shut down all nodes). It generally is a manual process that pretty much involves restoring from backup.
3. A lot of people know how to manage Postgres. Much less people know how to manage etcd in production.
4. Tooling for Postgres (to operate it, backup and restore, monitor, etc) is a lot more advanced.
5. Pretty much all cloud providers offer managed Postgres services. I don’t believe any one of them offers managed etcd.
> Pretty much all cloud providers offer managed Postgres services. I don’t believe any one of them offers managed etcd.
I think this is key. PostgreSQL is boring for sure (in a good way), but there is huge operational value in being able to point at a managed endpoint and move on to higher value work.
