关于Cassandra和MySQL的一点建议 [英] A bit of advice on Cassandra vs. MySQL

问题描述

我在几天前问了一个问题，并得到了一些很好的答案，我正在考虑做一个Facebook风格的网站，配置文件，生物的，等等，并问我是否应该使用mysql，答案是使用Cassandra因为它好多了。我只是问这是每个人都建议，它只是我知道mysql相当不错，这将是一个完全愚蠢的举动，我使用mysql对Cassandra（我甚至听说过直到2天前）

I asked a question on here a couple of days ago and got some really good answers, i'm thinking about doing a facebook style website with profiles, bio's, etc, and asked whether i should use mysql, the answers were to use Cassandra because its much better. I'm just asking is this what everyone would suggest, its just i know mysql fairly well and would it be a completely stupid move on my part to use mysql over Cassandra (which i hadnt even heard of until 2 days ago)

感谢

推荐答案

Cassandra将使开发变得困难，它仍然缺乏工具，教程等。它正在迅速变化，所以你必须改变你的代码。

Go for MySQL. Cassandra will make development hard, it still lacks tools, tutorials, etc. And it's rapidly changing, so you'll have to change your code as well.

在这篇文章 - 它解释了为什么我认为还没有时间正规项目去Cassandra。

Take a look at this article - it explains why I think it's not yet the time for regular projects to go for Cassandra.

如果您的应用程序暴雪，需要比MySQL提供更多的可扩展性，那么您将有足够的人来处理转换到Cassandra。只需提取您的数据访问层，以便稍后可以切换，而无需更改其余代码。

In case your application sky-rockets and needs more scalability than MySQL provides, then you'll have enough people to handle the transition to Cassandra. Just abstract your Data access layer so that you can later switch without changing the rest of the code.

更新：注意此答案的日期。根据定义，它会过时，因此请检查是否已经有好的工具，教程等。

Update: Note the date of this answer. It is by definition going to get out of date, so check if there are already good tools, tutorials, etc.

这篇关于关于Cassandra和MySQL的一点建议的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！