简体   繁体   English

Azure Service Fabric与Azure Service Fabric网格

[英]Azure Service Fabric vs Azure Service Fabric Mesh

After painstakingly trying to learn and try out Azure Service Fabric, I now see 'Azure Service Fabric Mesh'. 在努力学习和试用Azure Service Fabric之后,我现在看到了“ Azure Service Fabric Mesh”。 Struggling to identify the key differences. 努力找出关键差异。

This page states 'Service Fabric is the orchestrator that powers Service Fabric Mesh'. 此页面指出“服务结构是为服务结构网格提供动力的协调器”。 I am aware of the services that I can deploy to a SF cluster. 我知道可以部署到SF群集的服务。

How is SF Mesh any different? SF Mesh有何不同? Maybe just SF with additional focus on containerized apps? 也许只是SF,而且还更加关注容器化应用?

Think about SF Mesh as the serverless Service Fabric platform (you don't have do do any cluster / VM management). 可以将SF Mesh视为无服务器 Service Fabric平台(您无需执行任何群集/ VM管理)。 It instead lets you completely focus on the application. 相反,它使您可以完全专注于应用程序。

Read more about it here: What is Service Fabric Mesh 在此处了解更多信息: 什么是服务织物网

Service Fabric Mesh in my opinion is really another product compared to "just" Service Fabric. 我认为Service Fabric Mesh与“仅” Service Fabric相比,确实是另一种产品。 This is largely due the fact that Service Fabric gives you a set of programming models like the actor model and reliable services model for both statefull and stateless services. 这主要是由于Service Fabric为您提供了一套编程模型,例如针对有状态和无状态服务的参与者模型可靠服务模型 Service Fabric mesh does not offer these models! Service Fabric网格不提供这些模型! So that is the first fundamental choice you need to make. 因此,这是您需要做出的第一个基本选择。

Also, Service Fabric is a PaaS offering but you can also host it on-premises or in other cloud environments. 此外,Service Fabric是PaaS产品,但是您也可以在本地或其他云环境中托管它。 Something you cannot do with Service Fabric Mesh. 您无法使用Service Fabric Mesh做某些事情。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM