需要有关此类网站的技术或设计的建议吗？
所以，我决定建立自己的梦幻体育网站。
您知道可以从您最喜欢的联赛中挑选球员的网站类型，并且根据他们的表现，您可以在您的球队中获得一定数量的积分。所有类型的联赛和运动项目都有梦幻球队，我相信您知道我在说什么。
我还没有确定具体的运动或联赛，因为我希望基础知识适合不同类型的团队运动。
我自己对此也有一些期待。如果您能提出其他建议，我将很高兴听到。
- 我希望该网站是动态的，并且在游戏期间有很多访问量，但除此之外几乎只有静态内容。
- 玩家积分应在游戏过程中实时更新。
- 我需要一个列表，显示正在玩的每个游戏以及该游戏中每个玩家的得分。它还应该显示上场时间、进球数、助攻数等。
- 每个注册用户都可以看到他/她的球队的实时更新的得分和球员。
- 我需要扩展该网站，这样如果我一开始有 1000 个团队，那么最终可以有 500 万个团队。
- 我现在可能不需要语言支持，但谁知道将来会怎样。
基于这些先决条件，在语言（php、.NET、drupal 或其他 cms）、数据库（mysql、sqlserver、xml）和其他技术方面最好使用什么？
也许我用什么并不重要？
我想每个玩家积分的动态实时更新是我最需要帮助的地方。
提前致谢！
/尼克拉斯
已编辑
我可以使用包含特定比赛周以下数据的数组：
- 球员 ID
- 比赛分钟数
- 体育特定得分（进球、助攻、点球、黄牌、最佳球员奖金）等
- 当前比赛周的总得分
当比赛进行时我会将这些添加到数据库中，并将这些数据与之前的任何比赛周相加。加上球员身价、选择该球员的球队数量等。
So, I've just decided to build my own fantasy sports web site.
You know the type of site where you can pick players from your favourite league and depending on how they do you get a certain amount of points in your team. There are fantasy teams for all types of leagues and sports, I'm sure you know what I'm talking about.
I haven't settled for a specific sport or league just yet because I want the basics to fit to different types of team-based sports.
I have a few expectations on it myself. If you can come up with any other I'll be glad to hear them.
- I expect the site to be dynamic and have many visits during a game, but almost only static content otherwise.
- Player points should be updated in real-time during a game.
- I would need a list that shows each game being played and the points of every player in that game. It should also show minutes played, goals, assists etc.
- Each registered user would be able to see the points and players of his/hers team updated in real time.
- I need the site to scale so that if I start with 1000 teams I could end up with 5 million.
- I probably won't be needing language support right now, but who knows in the future.
Based on these prerequisites what would be best to use in terms of language (php, .NET, drupal or other cms's), database (mysql, sqlserver, xml) and other techniques?
Maybe it doesn't really matter what I use?
I guess the dynamic and real time update of each player's points is where I need help the most.
Thanks in advance!
/Niklas
EDITED
I could use an array with the following data for a specific game week:
- Player ID
- Minutes played
- Sport specific points(goals, assists, penalties, yellow cards, man of the match bonus) etc.
- Total points in current game week
When the game is over I'd add these to a DB and sum this data with any previous game weeks. Plus player value, number of teams that has selected this player, etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可能必须为您的“游戏”代码走定制路线 - 而不是使用 CMS，尽管根据您的经验，您可能能够利用框架（例如 CodeIgniter）来加速您的一些 DEV时间。
这种类型的网站与语言无关，但它取决于您正在查看的实际用户数量，以及要部署的最具可扩展性的解决方案/技术集。
您必须考虑的最大考虑因素之一是数据模型的设计及其所在的平台。
如果您希望处理接近实时的更新，您将需要集中精力使数据库查询/处理尽可能高效。
You are probably going to have to go down the custom route for your "Game" code - rather than using a CMS, although depending on your experience, you may be able to leverage a framework (e.g CodeIgniter) to speed up some of your DEV time.
This type of site would be pretty language agnostic, however it would depend on the actual numbers of users you are looking at as to the most scalable solution / set of techniques to deploy.
One of the biggest considerations you are going to have to look at would be the design of the data model, and the platform that this sits on.
If you want to be processing near to realtime updates, you are going to want to focus your efforts on making the DB queries / processing the most efficient possible.
您在这里没有讨论的一大考虑因素是缓存。我确信您网站上的一些数据将在很长一段时间内保持静态（例如每周总计等），并且有些数据将是非常实时的（但仅在比赛日期间）。
但是，在比赛日期间，您的流量会比非比赛日多得多，因此您会在短时间内收到大量对相同数据的请求。因此，采用良好的缓存策略将为您节省大量的 CPU 资源。我的想法是计算玩家的分数，然后每次缓存 1 分钟，因此每次请求特定玩家时，您都会从缓存中检索，而不是每次都重新计算。
One big consideration that you have not discussed here is caching. There is some data on your site that I am sure will be static for long periods of time (such as weekly totals etc), and there is data that will be very much real time (but only during match days).
However, during match days you will have a lot more traffic than non match days, and you will therefore have a lot of requests for the same data in a short period of time. Therefore, employing a good caching strategy will save you masses of CPU power. What I am thinking of, is to calculate a player's score and then cache for 1 minute at a time, therefore each time that specific player is requested, you are retrieving from a cache, rather than recalculating each time.