* DB for persistence, kv for speed and disk for scaling(?). Different parts of your app might fit one of these cases. Why not have them all under one API?
* Use protocols to scale, not backends
* Single interface to talk to db/kv store and disk
* In addition, use an SQL-like interface, if that's what floats your boat.
* Moving data between db/kv/disk is a server side operation.
Comments
* DB for persistence, kv for speed and disk for scaling(?). Different parts of your app might fit one of these cases. Why not have them all under one API?
* Use protocols to scale, not backends
* Single interface to talk to db/kv store and disk
* In addition, use an SQL-like interface, if that's what floats your boat.
* Moving data between db/kv/disk is a server side operation.
Exactly. I'm glad someone's paying attention.
Additionally, it's mostly a project I started on a dare that I started liking to hack on. Not really expecting anyone to use it for a while, if ever.