blocks|key|1267058|text|Twitter的大部分前端都在运行rails。动物群的客户端实际上是由twitter构建和发布的，因此您可以相当肯定它在大型工作负载上是最新的和稳定的。回顾提交的历史表明，经常会对其进行改进，这是很棒的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1267059|很可能需要定制Authlogic，以便与Cassandra一起正常工作。特别是，它似乎提供了基于named_scope和关系数据的某些方法。|1267060|确实有人在Authlogic中为DataMapper支持构建了一个插件：http://twitter.com/collintmiller/statuses/2064046718。你也许可以用它作为一个起点，使它与卡桑德拉兼容。|offset|length|1267061|祝好运!|1267062|entityMap|0|LINK|mutability|MUTABLE|url|http://twitter.com/collintmiller/statuses/2064046718^0|0|0|10|1G|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Twitter is running rails on most of their front end. Fauna's client is actually built and released by twitter, so you can be pretty certain that it's up to date and stable on large workloads. Looking at the history of commits shows that there are frequent improvements being pushed to it, which is great.

Most likely Authlogic would need to be customized to work properly with Cassandra. In particular, it appears to provide certain methods based on named_scope and relational data.

It does appear that someone has built a plugin for DataMapper support in Authlogic: <a href="http://twitter.com/collintmiller/statuses/2064046718" rel="noreferrer">http://twitter.com/collintmiller/statuses/2064046718</a>. You may be able to use that as a starting point for making it compatible with Cassandra.

Good luck!

blocks|key|1471959|text|我不认为从MySQL开始，然后搬到卡桑德拉是个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1471960|Cassandra是一个NoSQL解决方案，而MySQL是一个“经典”的SQL驱动数据库。|offset|length|1471961|这意味着你的模型会有所不同。|1471962|如果您从MySQL开始，您将不得不依赖ActiveRecord来创建您的模型。如果然后更改为Cassandra，则必须将所有模型更改为与NoSQL兼容的中间件(如BigRecord)。这不仅意味着更改您的模型，还意味着使用它们的控制器(因为它们的接口不同)。|1471963|这就是说，Cassandra等应该被用于非常苛刻的应用程序--比如twitter。|1471964|其他的网络应用程序没有那么强烈--你确定你还需要卡桑德拉吗？|1471965|PostgreSQL和一个设计良好的数据库，在98%25的时间里都是足够好的.|1471966|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/NoSQL|1|http://www.bigrecord.org/about/^0|0|C|5|0|0|0|29|9|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

I don't think starting with MySQL and then moving to Cassandra is a good idea.

Cassandra is a <a href="http://en.wikipedia.org/wiki/NoSQL" rel="noreferrer">NoSQL</a> solution, while MySQL is a "classic" SQL-driven database.

This means that your models would be different.

If you start with MySQL, you will have to rely on ActiveRecord for creating your models. If you then change to Cassandra, you will have to change all your models to a NoSQL-compatible middleware (such as <a href="http://www.bigrecord.org/about/" rel="noreferrer">BigRecord</a>). This not only means changing your models, but also the controllers that use them (since their interface would be different).

This said, Cassandra and the like are supposed to be used on very demanding applications - like twitter.

The rest of web applications out there are orders of magnitude less intense - are you sure you still would need Cassandra?

PostgreSQL, and a well-designed database, is just good enough 98% of the time.

blocks|key|1267084|text|还有对象，IIANM建立在动物群客户端之上。"Cassandra对象为使用Cassandra提供了一个很好的API。CassandraObjects主要是与ActiveRecord对象兼容的鸭子类型的，所以大多数控制器代码都应该正常工作……只有在您希望帮助开发的时候，才能在生产中使用它，现在有许多粗糙的边缘。“|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1267085|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/NZKoz/cassandra_object^0|2|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is also <a href="http://github.com/NZKoz/cassandra_object" rel="nofollow noreferrer">http://github.com/NZKoz/cassandra_object</a>, which IIANM builds on top of the fauna client. "Cassandra Object provides a nice API for working with Cassandra. CassandraObjects are mostly duck-type compatible with ActiveRecord objects so most of your controller code should work ok... Use this in production only if you're looking to help out with the development, there are a bunch of rough edges right now."

blocks|key|1267095|text|我现在正在研究卡桑德拉，MongoDB和CouchDB。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1267096|判断哪个项目有最多开发人员支持的方法之一是检查每个级别最高的github项目的观察者数量。至少作为粗略估计。|1267097|现在它是|1267098|852-MongoDB+http://github.com/jnunemaker/mongomapper|offset|length|1267099|544+-+CouchDB+http://github.com/jchris/couchrest|1267100|178-Cassandra+http://github.com/fauna/cassandra|1267101|虽然，我不得不说，与一群高知名度的网站(Twitter，Digg，Reddit等)最近宣布，他们将迁往卡桑德拉，这是一个巨大的信心投票给他们。|1267102|蒙戈似乎拥有迄今为止最丰富和最好的文档。他们的自动切分仍然是阿尔法，所以它的规模还有待观察，我认为。|1267103|我刚刚开始了解所有这些东西，所以如果其他人有洞察力，请分享。|1267104|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/jnunemaker/mongomapper|1|http://github.com/jchris/couchrest|2|http://github.com/fauna/cassandra^0|0|0|0|C|14|0|0|E|Y|1|0|E|X|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$H|19|I|1A|1|1B]]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@$H|1D|I|1E|1|1F]]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@$H|1H|I|1I|1|1J]]|A|$]]|$1|N|3|O|5|6|7|1K|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1L|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1M|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]|11|$5|W|X|Y|A|$Z|12]]|13|$5|W|X|Y|A|$Z|14]]]]

I'm researching Cassandra, MongoDB, and CouchDB right now.

One way to tell which has the most developer support, is by checking the number of watchers on the highest rated github project for each. At least as a rough estimate.

Right now it's

852 - MongoDB
<a href="http://github.com/jnunemaker/mongomapper" rel="noreferrer">http://github.com/jnunemaker/mongomapper</a>

544 - CouchDB
<a href="http://github.com/jchris/couchrest" rel="noreferrer">http://github.com/jchris/couchrest</a>

178 - Cassandra
<a href="http://github.com/fauna/cassandra" rel="noreferrer">http://github.com/fauna/cassandra</a>

Although, I have to say with a bunch of high profile sites (Twitter, Digg, Reddit, etc) recently announcing that they're moving to Cassandra, this is a big vote of confidence for them.

Mongo seems to have the most and best documentation so far. Their auto-sharding is still in alpha though so how well it scales still remains to be seen I think.

I'm just starting to learn about all this stuff, so if others have insight please share.

blocks|key|1472037|text|如果然后更改为Cassandra，则必须将所有模型更改为NoSQL。|type|blockquote|depth|inlineStyleRanges|entityRanges|data|1472038|这根本不是真的。如果您已经以这样的方式编程，您的MySQL+db执行了大量的连接，那么是的，您可能有一个问题。当我们开始MySQL路由时，我们从一开始就尽量避免加入。然后，当我们开始迁移到卡桑德拉，这是相当容易的，我们这样做的1模式，只是在一开始。然后一次说出4个模型。等。效果很好。事实上，当你阅读twitter的采访时，你会注意到他们在一段时间内并行运行MySQL和Casandra，同时运行相同的模型：http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king。|unstyled|offset|length|1472039|至于Authlogic，您可以将该部分保存在mySQL中，只要您愿意，只需将其与您的Cassandra数据松散耦合即可。|1472040|entityMap|0|LINK|mutability|MUTABLE|url|http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king^0|0|5O|2F|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@$E|S|F|T|1|U]]|A|$]]|$1|G|3|H|5|D|7|V|8|@]|9|@]|A|$]]|$1|I|3|-4|5|D|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<blockquote>
 If you then change to Cassandra, you will have to change all your models to a NoSQL
</blockquote>

This isn't true at all. If you have programmed in such a way that your MySQL db does loads of joins, then yes, you may have a problem. We avoided joins as much as we could from the beginning when we started the MySQL route. Then when we started migrating to Casandra it was fairly easy, we did so with 1 model only at first. Then say 4 models in one go. Etc. Works well. In fact, when you read the interview with twitter you'll notice they ran MySQL and Casandra in parallel for the same model for a while: <a href="http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king" rel="nofollow noreferrer">http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king</a>.

As to Authlogic, you can keep that part in mySQL for as long as you like, just keep it loosely coupled with your Cassandra data.

I'm working on a project that is considering using Cassandra as a database. We would like to eventually migrate to Cassandra even if we use MySQL to start with, given its scalability. I know that big companies like Facebook, Digg, and recently Twitter is using Cassandra, but I don't believe any of those sites run off Rails. My question is whether or not it's feasible to use Cassandra using Ruby on Rails. Points to consider:

<ol>
<li>We heavily rely on the Authlogic gem. Would switching to Cassandra affect how it works?</li>
<li>Are there any mature ruby clients for Cassandra? Looking on Github it seems that <a href="http://github.com/twitter/cassandra" rel="noreferrer">fauna's client (now twitters's client)</a> is the most mature. Has anyone had production experience with it?</li>
</ol>

Appreciate any tips.

Is Cassandra production ready for Ruby on Rails?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在做一个正在考虑使用Cassandra作为数据库的项目。考虑到MySQL的可伸缩性，我们希望最终迁移到Cassandra，即使我们一开始就使用它。我知道像Facebook、Digg和最近推特这样的大公司正在使用Cassandra，但我不相信任何这样的网站会偏离轨道。我的问题是，使用Rails使用Cassandra是...

问卡桑德拉的产品是否已经准备好用于Rails？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问卡桑德拉的产品是否已经准备好用于Rails？EN