Why Lark has its own storage format

Lark is a realtime database with a Firebase-compatible API, and the obvious way to build something like that is the way Supabase did it, where you write the realtime layer and the auth and the rules engine yourself, and then put all of it in front of a storage engine that already exists and already works. Postgres has been keeping people's data safe for thirty years and I have not, so that seemed…