对于要编写自己的数据库的人，您会建议读什么？
因为我之前的问题没有答案。我真的在考虑实现一个自定义数据库来满足我的要求。
是的，我知道，听起来很疯狂。
但是您会推荐阅读哪些书籍、文章等？
如果确实重要，我的数据库的要求遵循
- 面向图形的-针对存储图形和遍历进行优化（例如HyperGraphDB、Neo4j）
- 在内存中运行，但具有持久存储（例如Redis）
- 分布式（例如membase）
- 具有.NET适配器（TCP /IP，而不是 HTTP REST）
我不寻找技术细节，只是想找到一些关于通常如何完成事情以及我有什么选择的理论信息来源。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果您愿意在编码上花费精力，为什么不加入现有项目并根据您的需求进行调整/扩展呢？例如，透明分布和仅 RAM 数据（可选地持久化）都在 HyperGraphDB 的 TODO 列表中，因此我们很高兴您能提供帮助:)实际上，主要是主内存是 HyperGraphDB 的原始要求，但它有点考虑到它所用于的项目，它在某些时候变得无趣了。
干杯，
鲍里斯 (http://www.hypergraphdb.org)
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)
您可以对上一个问题开始悬赏，以获得更多关注。但对于这个问题，我建议“不要”。这听起来确实有点疯狂，您将花费数月（可能数年）的时间来创建一些只能对现有解决方案进行增量改进的东西。
可能值得发布该项目的更多详细信息并解释为什么您有这些要求。您可能可以通过不同的解决方案组合来满足您的所有要求（例如：为什么是＃2？为什么不能使用缓存而不是必须在内存中运行？）。
如果这是一个商业产品，那么我假设您有一个非常有趣的项目，需要烧很多钱。如果是个人项目，那么祝你好运，你比我勇敢多了！ ;-)
You could start a bounty on your previous question to get more attention for it. But as for this question, I would recommend "Don't." It does sound a little crazy, and you'll spend months (probably years) creating something that delivers only incremental improvement over an existing solution.
It might be worth posting some more details of the project and explaining why you have these requirements. It's possible that you could meet all of your requirements through a different combination of solutions (eg: why #2? Why can't you use caching instead of having to run in memory?).
If this is for a commercial product then I'm assuming you have a really interesting project with lots of money to burn. If it's for a personal project then good luck, and you're a lot braver than I am! ;-)
您是否尝试过 mongoDB http://www.mongodb.org/ ？我认为它满足您的要求。告诉我是否有。
干杯]：>
Did you try mongoDB http://www.mongodb.org/ ? I think it satisfy your requirements. Tell me if it does.
Cheers ]:>