Deno KV internals: building a database for the modern web | Deno details their use of FoundationDB at scale for a key-value store with a nice API to TypeScript. The striking feature is their introduction of an additional “transaction layer” on top of FDB, which I found surprising. The cited reasons are mostly around lack of additional pushdown predicates to limit the number of network roundtrips, if I understood correctly.
The HackerNews discussion of this Deno KV internals: building a database for the modern web | Hacker News has posts that share my surprise, while the Deno developer that did the FDB integration thinks that additional layer is pretty much necessary for their use case: losfair's comments | Hacker News
My question to the community: Is it really true that Deno had no alternative? Is there a simpler way that avoids a complex extra layer?
Any insights greatly appreciated!