托管 ASP.NET - 知识渊博的程序员，托管菜鸟 - 扩展和速度问题
对这个巨大的问题表示歉意......请耐心等待并尽力提供帮助:)
以前的雇主都拥有内部托管或除我之外的其他人来处理那方面的事情和我所有的个人项目（即低流量） servergrid.com 可以轻松处理，即使在其基本包中也允许任意数量的域。
我即将承担更严肃的项目，但对托管、要问的问题和要寻找的内容知之甚少。已经完成了一些基础研究，但老实说，当我主要关心的是速度和速度时，我对所涉及的指标数量感到困惑。缩放。
我注意到，例如，servergrid 数据库服务器共享许多 100 个数据库用户/服务器，因此我想象一个共享包，您每月只需支付 2 美元即可购买 SQL Server，虽然很便宜，但不会扩展到超出业余爱好站点。
那么：
- 迁移到专用或虚拟专用服务器是速度的简单答案，也是我需要担心的唯一真正指标吗？
- 专用定价是服务器网格上的一个巨大飞跃 - 是否有高级共享服务不会在服务器上放置大量人员 - 从网站上看似乎并不明显，这会产生巨大的差异吗？
- 情况似乎发生了很大的变化 - IIS7 和 Server 2008 似乎拥有所有这些 像独立应用程序池/ Hyper V 这样的功能，这些只是胡言乱语还是对扩展和速度有很大帮助的东西？
- 最后是云托管（特别是 http://www.rackspacecloud.com） - 它可以正确运行 .NET，是吗？在架构上与其他任何东西都有根本不同，还是只是使用云一词进行营销？它看起来很酷 - 但这只是普通的托管，具有不同的计费模型和更简单的扩展方式吗？这是否类似于大肆宣传的 squarespace 托管博客/网站系统？
抱歉我的问题漫无目的，并且非常感谢有人能够用相对简单的英语消除我的一些基本误解......
谢谢！
Apologies for this huge question.....please bear with me and try to help :)
Previous employers have all had in house hosting or people other than me to deal with that side of stuff and all my personal projects (ie low traffic) have been comfortably handled by servergrid.com who allow any number of domains even in their basic package.
I am about to take on more serious projects and have little clue about hosting, the questions to ask and what to look for. Some basic research has been done but I am honestly confused by the number of metrics involved when main thing i care about is SPEED & SCALING.
I have noticed that servergrid db servers for instance shares many 100s DB users/server so I imagine a shared package where your paying just 2$/month for sql server, tho a bargain, is not going to scale beyond a hobby site.
So:
- is moving to a dedicated or virtual dedicated server the simple answer to speed and the only real metric I need to worry about?
- dedicated pricing is a big jump on servergrid - are there premium shared services that don't put a bazillion people on the server - it doesn't seem obvious from the sites, would it make a huge difference?
- the landscape seems to changing in a big way - IIS7 and Server 2008 seem to have all these
features like Isolated Application Pools/ Hyper V, are these just BS hype or things that seriously help with scaling and speed? - Lastly cloud hosting (specifically http://www.rackspacecloud.com) - it runs .NET right, is it fundamentally architecturally different to anything else or just use of the word cloud for marketing? It looks v cool - but is it just normal hosting with a different billing model and a somewhat easier way to scale? Is this similar to the much hyped squarespace hosted blog/site system?
Sorry for my rambling style of question and would be deeply grateful for someone who can just in relatively plain english sweep away some of my basic misconceptions....
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
好的，请查看 Amazon Web Services。他们在基础设施（硬件和软件）方面非常灵活，我发现他们的费率还可以。此外，他们的商业模式围绕“使用”而不是“租赁”（即您根据使用的内容、使用时间等付费）。
我认为这是一个很好的起点。
Okay, take a look at Amazon Web Services. They are very flexible in terms of infrastructure (both hardware and software) and I find their rates to be ok. Also, their business model revolves around "using" not "leasing" (ie you pay based on what you use, for how long, etc).
I think it's a good starting point.
因为您主要关心的是“速度”和“速度”。 “规模”你也可以看看Windows Azure和SQL Azure
Windows Azure
Steve Marx 的精彩简短视频解释。
什么是 Windows Azure
Since your main concern is "speed" & "scale" you may also take a look at Windows Azure and SQL Azure
Windows Azure
A nice brief video explanation by Steve Marx.
What is Windows Azure
对于“更严肃的”生产部署，我会远离共享托管。亚马逊的 AWS 是一个很好的起点（rackspace 有类似的服务，现在支持自我配置）。如果做不到这一点，您可能会仔细评估您真正需要的规模。如果您知道您将拥有多少用户并且知道他们的使用模式是什么，那么就可以选择适合的专用托管。如果您的用户数量未知且不可预测，并且他们的使用量会激增，那么请选择 AWS。
这将是我的第一步方法。 YMMV，调整你自己的方法需要时间。
I would stay away from shared hosting for a "more serious" production deployment. Amazon's AWS is as good a place to start as any (rackspace has a similar service which now supports self-provisioning). Failing that, you might carefully evaluate how much scale you really need. If you know how many users you'll have and have any idea what their usage patterns will be, then get dedicated hosting to fit. If the number of your users is unknown and unpredictable, and their usage will be spiky, then go with AWS.
That would be my first-pass approach. YMMV, and it will take time to fine-tune your own approach.