Hi All, I'm investigating the possibility of using an external key-value store as the backing store for h2 db. Imagine something like Redis, memcache, or DynamoDB, as an alternative to the current two choices if in-memory vs filesystem storage. The end-goal is the ability to instantiate an "embedded" h2 that uses "dumb" (NoSQL) cloud storage to persist the data and index B-Trees, while retaining the full RDBMS SQL capability of the upper layers.
I've come down to a decision-point with three choices... 1) reimplement MVStore abstraction, 2) reimplement filesystem abstraction used by MVStore, or 3) implement pluggable tables, one layer up. A question to those more familiar with the code-base... Which of the above three lines of research is most likely to yield fruitful results? Thanks -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/9cc729a8-1395-4aa4-b2f1-a7eee74f215fn%40googlegroups.com.
