是什么让项目适合 Azure/云?
我已经阅读过有关 Windows Azure 的内容,但为了深入了解这项技术,我(显然)需要使用它。我有一个小型 ASP.NET 网站,流量很少,我认为在 Azure 上托管该网站会节省我的钱。除此之外,还有哪些因素会影响项目适合云?
谢谢
I have read about Windows Azure but to get deeper into this technology, I need to (obviously) use it. I have a small ASP.NET site which gets little traffic and I am thinking that hosting this on Azure would save me money. Other than this, what other factors would contribute to a project being suitable for the cloud?
Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
云通常包含四个基本原则:
因此好的云项目具有这些属性中的一个或多个。一些示例:
The cloud generally encompasses four basic principles:
So good cloud projects speak to one or more of these attributes. Some examples:
Azure 确实有所帮助,因为您的所有数据都更加“防丢失”,而且我认为 M$ 还使用某种内部加密,因此更安全。 “Azuring”您的网站的好处:
1. 允许您扩展站点和用户群,而无需提升代码并对硬件进行重大更改,这样您就可以快速成长,并且所有潜在问题都得到解决,因为只要你能适度支付(支付你使用的费用,而不是大量的一次性投资和定期维护)。网站崩溃、用户流失等过渡性灾难将被完全避免。
2. Azure很好地集成到.NET中;这种转变不会成为主要的学习障碍。昨天的一个晚上,我弄清楚了 blob 和表 api,以及如何将它们与我的一个项目集成。
缺点:
1. Azure 平台已经变化了很长一段时间,从某种意义上说,它不是一个成熟的产品,并且语法和功能将在一段时间内不断变化。 (尽管它们在很大程度上只是增强),所以对于某些人来说这可能是一个问题。
2.过渡的额外努力。
我的建议:如果你觉得的话就换吧
1.你对未来的增长有预期
2.想要学习和尝试新技术;并准备付出额外的努力。
Azure does help in the sense that all your data is more "loss proof", and I think M$ also uses some sort of internal encryption, so some what more secure. benefits of "Azuring" your site :
1. Allowing you to expand the site, and your user base without need to jack-up your code and make major changes to your H/W, so you can grow on the fly, and all the underlying issues are taken care off, as long as you can pay up modestly( pay what you use, rather than heavy onetime investments and regular maintainance). Transitional disasters of site crashes, user loss etc will be completely avoided.
2. Azure is very well integrated into .NET; the transition will not be a major learning hurdle. Yesterday in one night I was able to figure out the blob and the table api, and how to integrate them with on of my projects.
Disadvantages:
1. Azure platform has been in flux for a lot of time, in the sense that it is not a mature product and the syntax and features are going to be in flux for sometime. ( although they have only been enhancements for the most part), so that might be an issue, for some.
2. extra effort of transition.
my suggestion: shift if you feel
1. you are expecting growth in the future
2. want to learn and experiment with new technology; and ready to make an extra effort.