They both use KVs using LSMs, do range queries, support ACID transactions, handle resharding and clustering for you.
They're both based off of Spanner fundamentals. They both actually have an SQL layer - foundationdb's is the record layer. Just because one has a primary SQL interface doesn't mean we can't compare.
I'd really like to know a comparison of the fundamentals including hotspot management, resharding, read/write performance, resharding etc. also and have been looking for this.
Can you show me their SQL layer? I was looking for it.
There's a go and rust library floating around that's not as good. I've tried em :)
> Queries - The Record Layer does not provide a query language, however it provides query APIs with the ability to scan, filter, and sort across one or more record types, and a query planner capable of automatic selection of indexes.
So I'm not sure how you can call that a SQL layer when SQL is a query language and FDB Record Layer says it doesn't have a query language?
There were a couple SQL-ish things I found in other languages and got them mixed up. Sorry about that :)
https://forums.foundationdb.org/t/sql-layer-in-foundationdb/...
There is a relational layer you can run though called Foundation Record Layer. But this doesn't support SQL AFAICT. The examples on Github just show a query builder interface in Java [0].
There does seem to be a Lucene interface but it doesn't seem to be used [1].
[0] https://github.com/FoundationDB/fdb-record-layer/blob/main/e...
[1] https://forums.foundationdb.org/t/lucene-layer-on-foundation...