Disclosure: I'm the architect for a distributed database. We started building our database because we had similar problems with not being able to accept writes

Disclosure: I'm the architect for a distributed database. We started building our database because we had similar problems with not being able to accept writes when our Master went down. This is never fun, but you guys seemed pretty well prepared, staying true to your company's motto - thank you for writing this article. First off, if your data is primarily logs you should not have to rely upon a primary Master. PostgreSQL isn't designed to be Masterless, which presents an obvious barrier. If you set up a Master-Master database then any/all of your servers could accept writes, even if another one is down. And since they are logs, you are getting idempotent behavior for free anyways, as everything is create/insert you don't have to worry about concurrent updates to the same record - which is what Master based systems are designed for. I actually DO NOT recommend our database (http://gunDB.io/ http://gunDB.io/) because we are not stable or production ready in any way shape or form. But we're in our seed stage funding and trying to spend the time exploring problem spaces and designing solutions for them. If you ever have time to chat, please drop me a line at mark@gunDB.io so I can learn from you.