数据库替代MySQL为数百万TABLES [英] Database alternative to MySQL made for millions of TABLES

问题描述

我的理解是，MySQL的目的是拥有数百万行的表。我正在寻找一个数据库系统，设计有数百万的关系表。我是否纠正我的理解，MySql查询数据的方式使得这种实现的效率低？这是一个长期的，用户驱动的项目，因此可扩展性是必须的。

谢谢！

EDIT：
由于立即出现负面反应，我会解释一下自己。如果项目在时间上积累了强大的用户基础，百万的表将是一个问题。它将实现类似于Stack Overflow上的编辑系统;我考虑了各种解决方案，并决定我最喜欢的一个是使用关系表为每个分支的编辑。我假设有一些数据库框架为这种事情设计。这是真的被认为是坏的建筑吗？为什么它不只是一个异常类型的架构？

解决方案

您可以随时查看NoSql DB：
From ： http://nosql-database.org/

<下一代数据库主要解决一些
的问题：非关系型，分布式，开源和
水平可扩展。

编辑：可扩展是我拍摄的。

建议：
http://www.mongodb.org/

编辑：有关数据版本控制的有趣概念：
在MongoDB中实现数据版本控制的方法

My understanding is that MySQL is intended to have tables with millions of rows. I am looking for a database system designed to have millions of relational tables. Am I correct in my understanding that the way MySql queries data makes it inefficient for that sort of an implementation? It is for a long-term, user-driven project, so extensibility is a must.

Thanks!

EDIT: Due to the immediately negative reaction, I'll explain myself. "Millions" of tables would be an issue if the project lived to accumulate a strong user base in time. It would implement an edit system similar to that on Stack Overflow; I considered a variety of solutions, and decided the one I liked best was one using a relational table for each offshoot of edits. I assumed there was some database framework designed for that sort of thing. Is this really considered "bad" architecture? Why is it not just an abnormal type of architecture? What is "wrong" with doing something that way?

解决方案

You could always look towards a NoSql DB: From: http://nosql-database.org/

"NoSQL DEFINITION: Next Generation Databases mostly addressing some of the points: being non-relational, distributed, open-source and horizontally scalable."

Edit: Scalable is what I was shooting for..

Suggestion: http://www.mongodb.org/

Edit: Interesting idea about data versioning: Ways to implement data versioning in MongoDB

这篇关于数据库替代MySQL为数百万TABLES的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！