simpledb、sql azure、mysql +内存缓存
对于新的可扩展高流量全球电子商务网站 (asp.net) 项目，哪种技术最适合（最大可扩展性和性能，最小价格和维护）？
amazon simpledb、microsoft sql azure、mysql + memcached 组合或您的解决方案...
For a new scalable high traffic global ecommerce website (asp.net) project which technology fits best (max. scalability & performance, min. price & maintenance)?
amazon simpledb, microsoft sql azure, mysql + memcached combo, or your solution...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我对此类问题的一般回答是：
互联网不会解决这类问题。没有最佳答案，因为它取决于太多变量。
你需要花钱请人来建造
为你准备好了。
（还）不需要那种性能/可扩展性。只要你能便宜地购买和设计任何东西就可以过日子。当您确实需要这种级别的性能/可扩展性时，您将能够负担得起#2。
my general answer to this type of question is:
the internet isn't going to cut it for this type of question. there is no BEST answer because it depends on too many variables.
you need to PAY someone to build
it out for you.
don't need that kind of performance/scalability (yet). get by on whatever you can buy and design cheaply. by the time you really DO need this level of performance/scalability, you will be able to afford #2.
您的目标相互冲突，您必须根据哪些事情对您的项目最重要来做出决定。使用 SimpleDB 或 Azure 等第三方服务将是最低的入门价格和最低的总体维护费用。但它们无法超越在物理上靠近 Web 服务器的快速硬件上运行独立数据库所获得的性能。
可扩展性则是另一回事。您可以获得一个快速的数据库。您可以获得免维护的数据服务。但可扩展性取决于你。它取决于您的代码、架构、配置、选择的代码库以及查找和修复瓶颈的能力。没有人愿意陷入无法扩展的解决方案中。在每个角落，您都可以找到人们告诉您您还不需要这种可扩展性。但事实是您列出的所有选项都会扩展。
使用在线解决方案，您将为可扩展性付出代价，从长远来看，它们会更加昂贵。但并不是每个人都是著名博主和超级 DBA 乐意免费帮助您完成网站项目。因此，如果您重视时间或向 DBA 付费，在线解决方案可能会更便宜。
通过您自己的硬件和数据库安装，您可以通过初始现金支出获得初始可扩展性。这将带你走很长很长的路。您甚至可以使用 EC2 之类的东西来避免初始成本。如果您的时间超出预算，这可能是一个很好的解决方案。
对于性能/价格/维护问题，没有一个正确的答案。您必须做出有利的权衡才能得到正确的答案。
You have conflicting goals, and you'll have to decide based on which things are most important to your project. Using 3rd party services like SimpleDB or Azure will be the minimum price to get started and overall minimum maintenance. But they won't beat the performance you can get from running a stand alone database on fast hardware physically close to your web server.
Scalability is a different story. You can get a fast database. You can get a maintenance free data service. But scalability is on you. It's on your code, your architecture, your configuration, the code libraries you choose, your ability to find and fix bottlenecks. Nobody wants to get locked into a solution that doesn't scale. Around every corner you can find people to tell you that you don't need that scalability (yet). But the fact is that all the options you list will scale.
With the online solutions you will pay for that scalability and in the long run they will be more expensive. But not everyone is a famous blogger with uber-DBAs happy to help you with your website project for free. So the online solutions can be cheaper if you value your time or if you pay your DBA.
With your own hardware and database install you get the initial scalability with the initial cash outlay. And that will take you a long long way. And you can even use something like EC2 to prevent the initial costs. And if you have more time than budget this can be a good solution.
There is no one right answer to the performance / price / maintenance question. You have to make beneficial trade-offs to get your right answer.