Re:Postgres high-availability cluster with auto-failover and...
by lobster_johnson on Tuesday November 17, 2015 @11:44AM
(#10582240)
You guys seem to be creating a bunch of great little tools, but I wish you would spend more time on documentation.
For example, in this case it's not at all clear how the cluster management works, or even what the semantics are.
Re:Postgres high-availability cluster with auto-failover and...
by tylerflint on Tuesday November 17, 2015 @12:26PM
(#10582594)
I couldn't agree more. We literally just introduced the nanopack cloud-initiative on friday (https://blog.nanobox.io/nanopack-a-new-vision-for-automated-...). Bear with us, we'll get there!
Manatee didn't work for our use cases, which should not be interpreted as "manatee is bad". Here are a few of the reasons we forged a different solution:
- While node.js is a great language for many things, we didn't want the overhead of running the node.js/v8 runtime alongside postgres. 50M might seem negligible, but with thousands of postgres clusters for our clients every MB adds up.
- We didn't want the administrative overhead of managing a zookeeper cluster, and instead built the cluster management semantics directly into the yoke project.
- This may be different now, but at the time manatee was very heavily integrated into illumos/smartos. We really love smartos, but recognize that not all clients are able to use this tech.