问题描述
目标应用程序是一个中型网站，用于每小时支持几百到几千个用户，可以选择扩展。数据模型相当简单，缓存潜力相当高（读取到编辑操作的比例为10：1）。
Target application is a medium-sized website built to support several hundred to several thousand users an hour, with an option to scale above that. Data model is rather simple, and caching potential is pretty high (~10:1 ratio of read to edit actions).
当选择之间应该考虑什么一个关系型SQL数据库到一个NoSQL选项（如HBase和Cassandra）？
What should be the considerations when coming to choose between a relational, SQL-based datastore to a NoSQL option (such as HBase and Cassandra)?
推荐答案
对我来说，有什么特别的问题需要解决。如果需要ACIDity，请使用数据库;如果没有，那没关系。最后只需建立你的应用程序。让我引用：
To me, you don't have any particular problem to solve. If you need ACIDity, use a database; if you don't, then it doesn't matter. At the end just build your app. And let me quote NoSQL: If Only It Was That Easy:
这篇关于选择SQL / NoSQL的注意事项应该如何？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！