Comment by mrkeen

> A rigorously defined, modular key/value API with adapters for multiple database technologies

> A way to make your application portable across different database technologies

> Data store independence Are we restricted to using only a specific type of database technology, or can virtually any database technology be used by implementing a simple API, making it easy to change later if needed?

I do not want one of my storage implementations promoting itself to be the master of all other storage implementations. To put it another way, I will not depend upon Permazen to provide independence.

Storage solutions need to be able to hide behind something like `Future<V> put(K k, V v)` or get out of the way.