SQL 数据库适合存储许多玩家及其游戏吗？
我正在为一款非常受欢迎的游戏的新版本编写后端。 （超过 500 万玩家，每月超过 5000 万场游戏）。
SQL 作为保存玩家个人资料及其游戏的存储系统是一个不错的选择吗？也就是说，我担心连接在这么大的表上的性能。
这就是我们想要做的：
- 拥有一个“成就”机制（“你刚刚玩了第 10 000 场游戏”，或者“你已经玩了 N 天”），
- 能够为给定的玩家显示他的“记录”过去的比赛
I'm writing a backend for the newer version of a pretty popular game. (5M+ players, over 50M games per month).
Is SQL a good choice as a storage system to save the players' profile and their games ? Namely, I'm afraid of the performances of a join on such big tables.
Here's what we want to do :
- have an "achievement" mechanism ("You just played your 10 000th game", or "You have been playing for N days")
- be able to show, for a given player, his "track record" of past games
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
SQL Server 可以轻松处理更多的数据。例如，我知道 SQL Server 数据库可以跟踪股票市场的变化。但是您需要让数据库专家来设计高性能的大型系统。要求应用程序程序员进行此设计就像要求您的妇科医生治疗您的肺癌一样。
SQl Server handles far more data than that easily. I know of SQL Server databases that track stock market changes for instance. But you need to have a database sepcialist do the design for a high performance, large system. Asking an application programmer to do this design is like asking your Gynecologist to fix your lung cancer.
它应该可以毫无问题地处理它。我有一个包含超过 20 亿行的表，只要索引正确就可以了。
对于大型数据集，您还可以考虑此处进行表分区。
It should handle it with no problem. I have had a table with over 2 billion rows and as long as your indexing is correct it will be fine.
You also consider table partitioning here for large datasets.