Hi Thomas, I am comparing mvstore and leveldb from API perspective.
One thing I really like about leveldb is that both its keys and values are arbitrary byte arrays. While this is low level, it has two advantages - it clearly separates storage concerns from object serialization / representation - the api becomes very simple (no need for mvstore.type.DataType) mvstore has pluggable datatypes. But the API becomes a little awkward. Even though MVMap<K,V> uses generics, some methods are simply taking raw Objects as parameters for example: public V <../../../org/h2/mvstore/MVMap.html> *get*(java.lang.Object key) So it seems type safety is out the window. I wonder if it would be better instead to let the client of mvstore decide how to represent data in binary form. I bet many of us use google/protobufs, google/flatbuffer, cap'n'proto, etc - and its straightforward to convert these to/from byte[]. Thanks & regards, -Alex -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
