Cassandra 准备好迎接黄金时段了吗？
我开始研究 Cassandra，它提供的功能给我留下了深刻的印象，但同时我读到了 Reddit 在迁移到 Cassandra 后如何进行防火演习，以及 Twitter 决定不使用它来发布推文。虽然这些都是大约一年前的事，但我想知道最新版本是否已经准备好迎接黄金时段了？
I started looking into Cassandra and I am really impressed with what it provides, but at the same time I read about how Reddit had a fire drill after migrating to Cassandra, and about twitter deciding to not using it for tweets. Although those were about a year ago or so, I am wondering if the latest version is ready for prime time yet?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Netflix 广泛讨论了他们如何从Oracle 和 SimpleDB 完全交给 Cassandra。
几周前，Twitter 还在 Cassandra 峰会上讨论了他们如何将 Cassandra 用于多个项目； Reddit 早期遇到了一些容量不足的问题，但后来说，“[2010 年我们的流量增加了两倍多” ]，Apache Cassandra 为我们提供的透明可扩展性在很大程度上使我们能够利用有限的资源来实现这一目标。”
还有许多其他公司使用 Cassandra（DataStax 客户只是冰山一角）。
简而言之，Cassandra 正在为真实的公司解决真实的问题。只是不要指望 MySQL 就可以了。 DataStax 文档 是一个很好的起点。
（克里斯对 API 稳定性的看法是错误的：我们很清楚，在 0.7 之后，我们将严格维护向后兼容性，而且我们甚至对于模式更新和混合版本集群操作等“维护”操作，以实现无停机升级。我会另请注意，与许多“NoSQL”数据库不同，Cassandra 始终认真对待数据持久性。）
Netflix has talked extensively about how they are moving from Oracle and SimpleDB entirely to Cassandra.
Twitter was also at the Cassandra Summit a few weeks ago talking about how they use Cassandra for multiple projects; Reddit had some early problems with being under-capacity, but later said, "Our traffic more than tripled [in 2010], and the transparent scalability afforded to us by Apache Cassandra is in large part what allowed us to do it on our limited resources."
There are many other companies using Cassandra (and DataStax customers are the tip of the iceberg).
In short, Cassandra is solving real problems for real companies. Just don't go into it expecting MySQL and you'll be fine. The DataStax documentation is a good starting point.
(Chris is mistaken about API stability: we were clear that after 0.7 we would be strict about maintaining backwards compatibility, and we have, even for "maintenance" operations like schema updates and mixed-version cluster operation for downtime-free upgrades. I would also note that unlike many "NoSQL" databases, Cassandra has always taken data durability seriously.)
Cassandra 仍在大力开发中。 API 仍在变化，从这方面来说，产品并不稳定。仍然偶尔会出现一些小故障，还有一些问题需要解决。它仍然是一个非常年轻的产品，距离真正成熟还有很长的路要走。
话虽如此，Cassandra 非常强大，只要您能够以适合 Cassandra 优点的方式构建数据。换句话说，如果你发挥 Cassandra 的优势，我想你会发现它在这一点上“足够成熟”。已经有许多大型网站在使用 cassandra，在这方面，它肯定已经准备好迎接“黄金时段”（无论这真正意味着什么）。
它需要数年时间（如果有的话）才能拥有与 MySQL 等传统 DBMS 相同的声誉和稳定性。
Cassandra is still under very heavy development. The API is still changing, and in that respect, no the product isn't stable. There are still occasional glitches, and a number of kinks to be worked out. It is still a very young product with a long way to reach before actual maturity.
Having said that, Cassandra is quite capable, provided that you are capable of structuring your data in a manner suited to Cassandra's strong points. In other words, if you play to Cassandra's strengths I think you'll find that it's "mature enough" at this point. There are already a number of large sites that use cassandra, and in this regard it's certainly ready for "prime time" (whatever that really means).
It will be years (if ever) before it has the same reputation and stability as a traditional DBMS like MySQL.