It's quite hard to give advice based on the information given. There are definitely some alternatives that are setup fire and forget, but usually come with som

It's quite hard to give advice based on the information given. There are definitely some alternatives that are setup fire and forget, but usually come with some cost. Self hosting a clustered postgres or similar will not be hastle free. the simple alternative is to throw money at the problem, but based on your comment that doesn't seem to be an option. There are some pretty cool tools surrounding SQLight to maintain a continuous backup as well as some simple read-replcas for scale up. Another simple solution would be to use some managed no SQL, but cost can rise quite quickly with increased usage. I really think foundationDB would be a misstep, it's a lot of work and requires a really good understanding of the db in excess of how to use it properly.