tuple-database VS fdb-record-layer

I've been tooling around with "Tuple Database", which claims to be FoundationDB for the frontend (by the original dev of Notion).

https://github.com/ccorcos/tuple-database/

I have found it conceptually similar to Relic or Datascript, but with strong preformance guarantees - something Relic considers a potential issue. It also solves the problem of using reactive queries to trigger things like popups and fullscreen requests, which must be run in the same event loop as user input.

https://github.com/wotbrew/relic

FoundationDB is really just a set of structures and tools to build any type of database you want on top of a solid foundation.

"FoundationDB decouples its data storage technology from its data model. FoundationDB’s core ordered key-value storage technology can be efficiently adapted and remapped to a broad array of rich data models. Using indexing as an example, FoundationDB’s core provides no indexing and never will. Instead, a layer provides indexing by storing two kinds of key-values, one for the data and one for the index."

https://apple.github.io/foundationdb/layer-concept.html

Then existing standard layers like the Record layer, providing "(very) roughly equivalent to a simple relational database" providing structured types, index, complex types, queries, etc.

https://github.com/FoundationDB/fdb-record-layer

> That being said, I wish there were more layers as the functionality out of the box is very very limited.

The record layer https://github.com/FoundationDB/fdb-record-layer which allows to store protobuf, and define the primary keys directly in those is truly amazing:

https://github.com/FoundationDB/fdb-record-layer/blob/main/d...

This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]?

[1] https://github.com/FoundationDB/fdb-record-layer