Since there are no answers to my previous question. I’m really thinking to implement a custom DB which will satisfy my requirements.
Yes I know, sounds crazy.
But what books, articles and etc. would you recommend to read?
If it does matter the requirements for my DB are following
- Graph oriented – optimized for storing graphs and traversal(e.g HyperGraphDB, Neo4j)
- Running in memory, but having a persisted storage (e.g. Redis)
- Distributed (e.g. membase)
- Had .NET adapter (TCP/IP, not HTTP REST)
I don’t look for technical details, just want to find some source of theoretical information on how things usually done and what choices do I have.
If you are willing to spend effort in coding, why not join an existing project and adapt/extend it to your needs? For instance, both transparent distribution and RAM only data (optionally persisted) are on the TODO list of HyperGraphDB, so we’d be happy to have you help out 🙂 Actually, being mainly main memory was in HyperGraphDB’s original requirements, but it kind of became uninteresting at some point given the projects it got used for.
Cheers,
Boris (http://www.hypergraphdb.org)