Scalaris 与 CouchDB
我需要为其中一个应用程序使用文档存储。我假设 scalaris 和 couchdb 与文档存储具有可比性。您对这两种解决方案有什么经验可以分享吗？您认为其中一个比另一个更好吗？
scalaris 的交易对我很有吸引力。由于缺乏 Erlang 背景，我对基于 Erlang 构建的解决方案更加信任。 riak 是我发现的另一个有趣的。因此，请分享您的想法或指向有关它们的更多信息。
I have this requirement to use a document store for one of the applications. I am assuming scalaris and couchdb are comparable as document stores. Do you have any experiences to share on these two solutions? Do you think one is better than the other?
transactions are attractive to me from scalaris. With little erlang background I have more trust on solutions built on Erlang. riak is another one I found interesting. So please share your thoughts or pointers to more information on them.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为你需要在这个领域进行更多研究。
键/值存储中键的类型显然很重要，但是您需要更准确地了解其余要求。分销策略等因素决定了可用性和一致性。您想要存储多少数据？也许MySQL还可以？您想要执行什么类型的查询？把它写下来并尝试适合每个解决方案！
我能说的是：
以上所有内容都有重要的工业用例。 Scalaris 似乎相当科学。
根据检索数据的方式，有许多原始解决方案，例如图形数据库或 Redis（比如丰富的 k/v 存储）。
I think you need more research in this area.
Type of a key in key/value store is obviously important, however you need to be more precise about rest of the requirements. Things like distribution strategy shapes availability and consistency. How much data do you want to store? Maybe MySQL is still all right? What kind of query you want to perform? Write it down and try to fit to each solution!
What I can say:
All of above have serious industrial use-cases. Scalaris seems to be rather scientific.
Depending on the way you will retrieve data, there is lots of original solutions like Graph databases or Redis (lets say rich k/v store).