In a globally distributed database, the main problem is time control because different locations have different clocks. For example, assume that one table of the database is located on Earth while another table is stored on Mars (4-13 minutes delay). Now we want to commit a transaction with these two tables from the moon while the result will be queried from Venus. I could not understand from this post if Fauna is able to correctly work under such conditions and whether it was designed for such use cases.
Interesting but ultimately irrelevant since it appears to not be FLOSS. We have already seen what happened to FoundationDB.
> industry experience has taught us that availability—in the strict sense that it is defined in the CAP theorem—is overrated: In practice, the uptime of systems that favor availability have not proven greater than what can be achieved with consistent systems.
The answer to any distributed consistent database is always the same: we gave up on one letter in CAP. In this case, it was 'A', availability.
And hey, cool, that's certainly an option. But I'd prefer if they had simply made that the subtitle.
I started using CockroachDB  recently and I'm really impressed with it overall. The Postgres compatibility is genius in my opinion, and despite some hurdles it's been a joy to work with (I'm using xo  to generate Go code from custom templates). I've yet to deploy it in production, but the best part is that if the performance sucks I can simply deploy postgres instead. As someone who used to be a big RethinkDB supporter, this is my new favorite pet oss project.
edit: oh, and it's written in Go, my main language, which is definitely a plus if you're a gopher