I want to develop web application which will be keeping results of game of teams within last 100 years and add actual results. My problem is that i don't know which data relation model should i choose relational or NoSQL. I have many years of experience with relational databases.
我想开发Web应用程序,它将在过去100年内保持团队游戏的结果并添加实际结果。我的问题是我不知道应该选择哪种数据关系模型关系或NoSQL。我有多年的关系数据库经验。
Data sample: TEAM A : Team B
数据样本:团队A:团队B.
Result 2:0.
I want to keep this event as win for Team A and loose for Team B.
我想让这个赛事成为A队的胜利,而B队则是松散的。
I want to query such information:
我想查询这样的信息:
- Wins and looses for team A
- Wins and looses for team B
- Team A meet Team B n times in history with Y wins and Z looses.
A队的胜利和失败
B队的胜利和失败
A队在历史上遇到了B队n次,Y胜和Z失败。
I suppose to have less then 1.Mi of play records.
我想有不到1.Mi的比赛记录。
Which important pros and cons should i consider by choosing the data layer? Which data model is better for performance to calculate these facts?
我应该通过选择数据层考虑哪些重要的优缺点?哪种数据模型更适合计算这些事实的性能?
Thank you in advance.
先谢谢你。
1 个解决方案
#1
0
With a database of this size, it really doesn't matter.
有了这个大小的数据库,它真的没关系。
Really you should consider how the data will be accessed and your familiarity with relational or MongoDB.
您真的应该考虑如何访问数据以及您对关系数据库或MongoDB的熟悉程度。
Personally I consider myself better with Mongo so i would use that - but the only reason would be personal opinion.
我个人认为自己对Mongo更好,所以我会用它 - 但唯一的原因是个人意见。
To answer: The best solution is the one you are most comfortable developing - with DB of this size there is no performance issues with either. assuming you stick to best practices.
回答:最好的解决方案是您最开发的解决方案 - 使用这种大小的DB,两者都没有性能问题。假设你坚持最佳实践。
#1
0
With a database of this size, it really doesn't matter.
有了这个大小的数据库,它真的没关系。
Really you should consider how the data will be accessed and your familiarity with relational or MongoDB.
您真的应该考虑如何访问数据以及您对关系数据库或MongoDB的熟悉程度。
Personally I consider myself better with Mongo so i would use that - but the only reason would be personal opinion.
我个人认为自己对Mongo更好,所以我会用它 - 但唯一的原因是个人意见。
To answer: The best solution is the one you are most comfortable developing - with DB of this size there is no performance issues with either. assuming you stick to best practices.
回答:最好的解决方案是您最开发的解决方案 - 使用这种大小的DB,两者都没有性能问题。假设你坚持最佳实践。