Azure的应用程序服务的Azure VS布服务 [英] Azure App Service vs Azure Service Fabric

问题描述

谁能告诉我的东西，将解释时，我应该创建一个Azure的服务应用布VS蔚蓝的应用程序服务应用程序？我有一个应用程序，我想建但不能确定我是否应该使用Azure的服务织物或Azure的应用服务构建它。

Can anyone direct me to something that will explain when I should create an Azure Service Fabric application vs an Azure App Service application? I have an application I want to build but can not determine whether I should build it using the Azure Service Fabric or the Azure App Service.

推荐答案

不幸的是，不是时使用何种任何官方指导。他们是两个不同的平台，遵循不同的发展模式。

Unfortunately there isn't any official guidance about when to use what. They're two separate platforms, following different development paradigms.

应用服务会给你功能，服务结构不提供开箱即用。如自动规模，认证，速率限制，与SaaS应用集成等部分或所有这些东西的东西可以来服务织物渐渐的，但我要说的是，在一分钟，他们针对不同的观众 - 一个缺乏经验的团队可能会发现很容易与App服务工作。

The App Service will give you functionality that Service Fabric doesn't provide out of the box. Stuff like auto-scale, authentication, rate limiting, integration with SaaS applications, etc. Some or all these things may come to Service Fabric gradually, but I'd say that, at the minute, they're targeted at different audiences - a less experienced team might find it easier to work with the App Service.

服务织物另一方面使部件更容易的组合物。例如，在传统的方式，如果你有这充分说明一个数据存储和缓存，以避免锤击数据存储的API，你必须处理各种容错方案。随着服务织物缓存能够可靠集合API进程中坐，你将不必处理具有外部缓存组件。数据被协同定位的服务（更快检索/编辑！）和因为它的整个服务被部署到所有节点分布是可靠的。类似的事情与队列。如果你认为一个工作流类型系统，在这里有一个API，作业服务，以及它们之间坐镇，并允许他们进行通信的队列，你需要管理3个不同的组件和它们之间的通信。随着服务架构中的队列进入应用程序。而这只是它的一半:)你也可以得到使用分布式计算的角色模型没有通常并发头痛的力量。最后，服务布艺你有你的本地主机更完整的开发环境的好处 - 你不必处理创建队列等上的Azure开发帐户或类似的东西。

Service Fabric on the other hand makes composition of parts easier. For example, in the "traditional" approach, if you had an API that speaks to a data store and a cache to avoid hammering the data store, you'd have to handle the various fault tolerance scenarios. With Service Fabric your cache can sit within the API process in a reliable collection and you won't have to deal with having an external cache component. The data is co-located with the service (faster to retrieve/edit!) and is reliable as it's distributed across all the nodes the service is deployed into. Similar thing with queues. If you think of a workflow type system, where there is an API, a job service, and a queue that sits between them and allows them to communicate, you'd have to manage 3 different components and the communication between them. With Service Fabric the queue comes into the application. And that's just half of it :) you also get the power of using the actor model for distributed computation without the usual concurrency headaches. Finally, with Service Fabric you get the benefit of having a more complete development environment on your local box - you don't have to deal with creating queues, etc. on an Azure dev account or anything like that.

另外值得一提的是，没有什么利用两种范例阻止你 - 想象与其中至少有一个是服务结构的应用程序，即公开的API，并且在这些上面的一个逻辑应用两个应用程序

Also worth noting that there's nothing stopping you from using both paradigms - imagine two apps with at least one of them being a service fabric app, that expose APIs and a logic app that sits on top of those.

您的决定应​​该基于你正在试图建立在多少时间什么，当你想释放（服务面料目前只在私人preVIEW因此这将是一段时间，直到他们得到GA），什么样的团队你。我想，与应用程序服务，它会很容易打到运行，即使你没有大量经验丰富的团队在地上，但服务面料会给你更多的力量，灵活性和控制。

Your decision should be based on what you're trying to build, in how much time, when you want to release (Service Fabric is currently only in private preview so it'll be a while until they get to GA) and what kind of team you have. I imagine that with the App Service it'll be easy to hit the ground running even if you don't have a massively experienced team, but Service Fabric will give you more power, flexibility and control.

这篇关于Azure的应用程序服务的Azure VS布服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！