I agree with the boring database, it's most often the good choice. Elaborating on my comment though, it would make sense to consider a drop-in replacement for

I agree with the boring database, it's most often the good choice. Elaborating on my comment though, it would make sense to consider a drop-in replacement for a technology for which you've already invested yourself, but got bitten enough time to think about moving away to a different model (operational burden, data loss, etc). I'm not sure if "baroque" is a good qualifier for FDB. It's recent in the open source community, but has been running in production for many companies (including Apple) for some years. It's based on sound architecture, compare to many others.