何时应使用以下各项:Amazon EC2、Google App Engine、Microsoft Azure 和 Salesforce.com?

发布于 2024-08-07 03:50:40 字数 1429 浏览 3 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(7

乙白 2024-08-14 03:50:40

好问题!正如您所指出的,不同的产品属于不同的类别:

EC2 是基础设施即服务;您获得虚拟机实例,并按照您的意愿使用它们。 Rackspace 云服务器或多或少是相同的。

Azure、App Engine 和 Salesforce 都是平台即服务;不过,它们提供了不同级别的集成:Azure 几乎允许您运行任意后台服务,而 App Engine 则面向短期请求处理程序任务(尽管它也支持任务队列和计划任务)。我对 Salesforce 的产品不是很熟悉,但我的理解是,它在某些方面与 App Engine 类似,尽管更针对其特定的利基市场。

软件即服务的云产品包罗万象,从 Amazon 的 Simple Storage Service 和 SimpleDB 等基础设施到 Fog Creek 托管的 FogBugz 等完整应用程序,当然还有 StackExchange。

一个好的一般规则是,产品的级别越高,您需要做的工作就越少,但它也越具体。如果你想要一个 bug 跟踪器,使用 FogBugz 显然是最省事的;在 App Engine 或 Azure 之上构建一个工作量更大,但提供了更多的多功能性,而在 EC2 等原始虚拟机之上构建一个工作量更大(事实上,要多得多),但提供了更多的多功能性。我的一般建议是选择仍然满足您的要求的最高级别的平台,并从那里开始构建。

Good question! As you point out, the different offerings fit into different categories:

EC2 is Infrastructure as a Service; you get VM instances, and do with them as you wish. Rackspace Cloud Servers are more or less the same.

Azure, App Engine, and Salesforce are all Platform as a Service; they offer different levels of integration, though: Azure pretty much lets you run arbitrary background services, while App Engine is oriented around short lived request handler tasks (though it also supports a task queue and scheduled tasks). I'm not terribly familiar with Salesforce's offering, but my understanding is that it's similar to App Engine in some respects, though more specialized for its particular niche.

Cloud offerings that fall under Software as a Service are everything from infrastructure pieces like Amazon's Simple Storage Service and SimpleDB through to complete applications like Fog Creek's hosted FogBugz and, of course, StackExchange.

A good general rule is that the higher level the offering, the less work you'll have to do, but the more specific it is. If you want a bug tracker, using FogBugz is obviously going to be the least work; building one on top of App Engine or Azure is more work, but provides for more versatility, while building one on top of raw VMs like EC2 is even more work (quite a lot more, in fact), but provides for even more versatility. My general advice is to pick the highest level platform that still meets your requirements, and build from there.

凡间太子 2024-08-14 03:50:40

这是一个很好的问题。完全公开,因为我偏爱 Azure,但有其他方面的经验。

我认为 Azure 与其他产品相比的突出之处在于从本地到云的快速过渡。例如 -

  • SQL Azure - 更改连接字符串,上传数据库,开始!
  • 队列的工作方式很像 MSMQ。
  • 无论你如何摇晃,斑点都几乎是斑点,但它们会疯狂地缩放。
  • 表存储组件很好,因为它为名称/值对提供了令人难以置信的可扩展性 - 但需要一些时间来适应。
  • 服务总线是我最喜欢的服务,因为它允许多种通信范例。两个 SB 端点首先尝试相互连接,如果无法连接,则它们通过云进行路由 - 当防火墙往往会妨碍时,可以实现非常安全和可扩展的处理。
  • 访问控制列表 - 通常与服务总线配对,以确保正确的人员访问正确的内容 - 想想云中的 SAML。

我希望这有帮助!

This is an excellent question. Full disclosure as I am partial to Azure but have experience with the others.

Where I think Azure stands out from the others is the quick transition from on prem to the cloud. For example -

  • SQL Azure - change connection string, upload DB, go!
  • Queues work a lot like MSMQ.
  • Blobs are pretty much blobs any way you shake them but they scale like crazy.
  • The table storage component is good because it provides incredible scalability for name/value pairs - but takes some getting used to.
  • Service Bus is my favorite of the services because it allows for a variety of communications paradigms. Two SB endpoints first try to connect to each other, if they cannot, then they route through the cloud - makes for very secure and scalable processing when firewalls tend to get in the way.
  • Access control list - paired typically with the service bus to make sure the right people access the right things - think SAML in the cloud.

I hope that helps!

女皇必胜 2024-08-14 03:50:40

我的云体验目前仅限于 Salesforce.com

对于标准业务运营和自动化,它提供了大量功能,使我们能够非常快速地启动和运行应用程序。我们特别受益于以下方面:

  • 安全性(管理员可以控制对对象和字段的访问
  • )批准
  • 自动 UI 生成
  • 内置报告和仪表板
  • 整个系统(包括我们的自定义更改)可通过 Web 服务
  • 访问 能够通过公共站点(例如电子商务)提供系统中的数据
  • 大型第三方应用程序库,用于解决标准问题

平台并不能解决所有问题。

我不会使用该平台来模拟核电站或构建下一个推特。

My cloud experience is currently limited to Salesforce.com

For standard business operations and automation it provides a significant number of features that allow us to get apps up and running very quickly. We are particularly benefitting from the following:

  • Security (Administrators can control access to objects and fields)
  • Workflow & Approvals
  • Automatic UI generation
  • Built in reporting and dashboards
  • Entire system (including our custom changes) is accessible via web services
  • Ability to make the data in the system available through public sites (e.g. eCommerce)
  • Large library of third party apps to solve standard problems

The platform does NOT solve every problem.

I would not use the platform to model a nuclear power station or build the next twitter.

在风中等你 2024-08-14 03:50:40

云计算的要点是通过付费使用来节省成本并实现计算资源的即时部署。

成本并不纯粹是每个实例每小时 x 美分。成本包括维护、开发、管理等。在我看来,云的巨大好处是将客户从管理任何不属于其核心业务能力范围的事情中解放出来。如果我是一家保险企业,我希望我的开发人员专注于我的保险问题,帮助解决我的索赔、费率等需求。我宁愿避免处理电子邮件服务器、文件服务器、文档存储库和管理操作系统补丁的问题 。

因此,在我看来,最大的好处来自于 SaaS 和 PaaS 云产品 仅当 PaaS 或 SaaS 对特定需求有严重限制时(即我需要安装一组专有 COM 组件而 Azure 不支持它们),才应使用 IaaS。

SaaS 适合商品类型的应用程序,这些应用程序不是客户的核心业务,而是更多的实用程序。这些是典型的消息系统、门户、文档存储库、电子邮件系统、CRM、ERP、会计等。当您可以自定义受良好支持的第三方产品时,为什么要通过编写自己的系统来重新发明轮子。

PaaS 非常适合支持公司主要业务的核心业务软件。让客户免于处理操作系统管理的麻烦,让客户专注于业务系统开发——这是其他人无法为客户做的事情。

The major points of cloud computing is to save on costs by paying for usage and enable immediate deployment of computing resources.

The costs are not purely x amount of cents per instance per hour. The costs include maintenance, development, administration, etc. The huge benefit of cloud, in my mind is to liberate the customers from having to manage anything that is not within the realm of their core business competency. If I am an insurance business, I want my developers to concentrate on my insurance problems that help solve needs of my claims, rates, etc. I would rather avoid dealing with problems of email servers, file servers, document repositories, and administrating OS patches, service packs, etc.

Thus, in my opinion, the biggest benefits are derived from the SaaS and PaaS cloud offerings. One should go to IaaS only when PaaS or SaaS have serious restrictions to specific needs (i.e. I need to install a set of proprietary COM components and Azure does not support them).

SaaS is good for commodity type of applications that are not the core line of business for the client, but are more of a utility. These are your typical Messaging systems, Portals, Document Repositories, Email systems, CRMs, ERP's, Accounting, etc. etc. etc. Why reinvent the wheel by writing your own when you can customize a well supported third party product.

PaaS is great for core line of business software that supports companies' main business offering. Abstracts clients from having to deal with OS management and lets clients concentrate on the business system development - something that noone else can do for the client.

霓裳挽歌倾城醉 2024-08-14 03:50:40

人们还可以利用 PaaS(例如 Google App Engine)的优势,并在必要时通过从 IaaS 提供商(例如 Amazon)中取出一些虚拟机来进行一些数字处理,然后将其发回,从而扩展它输出到 Google App Engine。

通过这种方式,您可以两全其美 - 您可以在 GAE 中快速开发可扩展的应用程序,然后您可以随时通过从 Amazon 虚拟机运行您想要的任何程序来增强它。

One can also take advantage of the benefits of PaaS (let's say, Google App Engine) and extend it, at times and if necessary, by pulling out some virtual machines from IaaS providers (e.g. Amazon) to do some number crunching then just send back the output to Google App Engine.

This way, you get the best of both worlds -- you can rapidly develop scalable apps in GAE, then you can always augment it by running any program you want from Amazon virtual machines.

放血 2024-08-14 03:50:40

这种情况一直在变化,现在Windows Azure也支持VM,所以它现在也是一个IaaS提供商。

This keeps changing, now Windows Azure also supports VM, so it is also an IaaS provider now.

遇见了你 2024-08-14 03:50:40

现在免费使用 Amazon EC2 一年怎么样,以便做一个更好的比较。看看这个。

http://www.buzzingup。 com/2010/10/amazon-announces-free-cloud-services-for-new-developers/

Now how about Free Amazon EC2 for a year to do a better comparision. Check this out.

http://www.buzzingup.com/2010/10/amazon-announces-free-cloud-services-for-new-developers/

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文