Feasibility of modifying to use Amazon DynamoDB in place of filesystem about jdbm3 HOT 5 CLOSED

Hi,

JDBM currently have those layers (from consumer down to raw disk)

1. collection with index (BTree, HTree)
2. instance cache
3. serialization
4. primitive record key-value store (long as key, byte[] as value).
5. disk store (ram, zip, file)

And if I understand correctly, this proposal is about JDBM using alternative implementations at level 4. I think this is very good idea and will definitely implement it.

My idea is: JDBM will export one more interface called RecordManager with methods like this:

long insert(byte[]) //insert new record, returs recid
void delete(long)  //delete record by recid
void update(long,byte[]) //update record with given recid with new data
boolean supportTransaction()
void roolback()
void commit()

User may supply alternative implementation in DBMaker. In this case JDBM will use other db as back-end, but user will still get instance cache, collections, serialization and other honey JDBM provides.

Only problem is that I am not going to write wrapper for DynamoDB (have no access to Amazon WS). Reference wrapper implementation will use LevelDB or Tokyo Cabinet. JDBM will also still support only single transaction per store.

ETA 2 weeks.

from jdbm3.

Thank you for the reply! I'll check back in a couple of weeks.

from jdbm3.

Hi,
JDBM now has very basic support for alternative key-value stores. Checkout RecordManager interface to give you some basic understanding. But it is still not finished.

https://github.com/jankotek/JDBM3/blob/master/src/main/java/net/kotek/jdbm/RecordManager.java

from jdbm3.

I decided not to implement this. Multiple key-value would complicate design too much. I reverted previous GIT commit

from jdbm3.

ok, thanks for letting me know.

from jdbm3.