将 RDBMS 过渡到 Cassandra 的迭代步骤/最佳实践
从 RDBMS 过渡到 Cassandra 的迭代步骤/最佳实践是什么？在移动之前对 RDBMS 模式进行非规范化是否有好处（除了提高 RDBMS 本身的可扩展性之外）？
What are the iterative steps / best practices for transitioning from an RDBMS to Cassandra? Is there a benefit to denormalization of the RDBMS schema prior to the move (beyond the improved scalability of the RDBMS itself)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个很大的问题。
我首先会阅读数据模型，特别是“思考查询”部分。
目标是为您需要执行的每个“操作”执行尽可能少的查询。这通常需要非规范化，有时需要不止一种方式。有时还需要使用很多技巧才能达到该目标；链接文档中的 Twissandra 示例演示了一些常见的示例。
当您有具体要求时，更容易给出具体建议。
That's quite a question.
I would start by reading about the data model, especially the "Thinking in Terms of Queries" section.
The goal is to do as few queries per "action" that you need to perform as possible. This frequently requires denormalization, sometimes in more than one way. There are also quite a few tricks that sometimes need to be used to reach that goal; the Twissandra example in the linked documentation demonstrates a couple of common ones.
It's easier to give specific suggestions for specific requirements, when you have them.