Cool to see this (I’d somehow missed the early access link until last night). Your storage strategy makes sense - building from first principles. To be honest,

Cool to see this (I’d somehow missed the early access link until last night). Your storage strategy makes sense - building from first principles. To be honest, I figured you’d not done that though, and I imagine this makes portability a bit harder. I’m eager to play with the service, but I wonder how local access patterns (e.g. dev workflows) differ - upon the right abstraction it shouldn’t really matter, right? I.e. a conn is a conn and a cursor is a cursor - the storage is opaque to the client. But does this somehow fall over with transactions and connection limits?