search

Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82 stars 13 forks source link

Why the name "Azure Service Fabric Mesh"? #206

Closed tomkerkhove closed 6 years ago

tomkerkhove commented 6 years ago

I'm a bit curious why the name Azure Service Fabric Mesh was chosen. Have other options been considered where the name Service Fabric is not used?

I totally see why it has been done but I'm also afraid that this will scare non-SF customers because "they don't use Service Fabric" while you really don't have to use it, just bring your containers.

That's why I think that names such as Azure Container Mesh could be a good replacement as it's not tied to Service Fabric and is a higher level of container abstraction than Azure Container Instances.

I know this is a bit close to Public Preview but I've been wondering about this for a while so now is the time before it goes out.

/cc @ChackDan

SamirFarhat commented 6 years ago

It's tied to Service Fabric. I don't have the mid-lingvterm roadmap, but it's likely that it will support Service Fabric apllication model, not just containers. Also, the Service Fabric features will be brought to SFM like Relibale collections, HA volumes and others.

tomkerkhove commented 6 years ago

That's right, but do all customers care that it's running on Service Fabric? Some do, some don't, some might be thinking that it's only for SF apps.

piizei commented 6 years ago

I did a bit of testing with the name in our organization, and indeed developers with background on open-source and java considered it something they would not never touch. 'service fabric mess' was the most heard comment. Think about it: if you would have something like this that can do serverless with custom containers and also run java-applications, would you call it Java Enterprise Edition Mesh? Hardly... 😃

tomkerkhove commented 6 years ago

Agreed, me as a customer do not care what infrastructure is beneath it, as long as it works. If it's related to Service Fabric I would expect that to show up in the docs and tell me if I really need to/care.

Another aspect is that it also limits its future where if MSFT decides to support other orchestrators or so, that the name will no longer make sense. For example if there will be an AKS version added where you select the orchestrator API (similar to Cosmos DB).

That said, I think it's also including Service Fabric as a branding option which I can see have value but I think a more general/generic name would be best for the success of the product in both long & short term.

Most reaction I'm expecting with public preview is:

We don't use Service Fabric so it's not for us

SamirFarhat commented 6 years ago

Waw, i didn't expected that a name could have such effect. If developers don't like Service Fabric, that is a different subject. First, SFM is a brand of SF, it's the managed version of SF, so it's tied to it. Second, SF is being Open-Sourced, so the Argument of Proprietary is no longer valid. Third, anyone will see that SFM will use the same terms than SF (app, service, replica, partition...), We will see even shared documentation, so soon or later we will discover it.

ChackDan commented 6 years ago

Thankyou Tom, Petteri and Samir for the discussion... The name ” Service Fabric Mesh” was already announced at the build/2018. So at this time we cannot change it, unless we find out something during preview. Do keep a look out for any customer reactions that you come across and share it with us..

From: Samir Farhat (MVP) notifications@github.com Sent: Sunday, July 8, 2018 11:44 PM To: Azure/service-fabric-mesh-preview-pr service-fabric-mesh-preview-pr@noreply.github.com Cc: Chacko Daniel chackdan@microsoft.com; Mention mention@noreply.github.com Subject: Re: [Azure/service-fabric-mesh-preview-pr] Why the name "Azure Service Fabric Mesh"? (#206)

Waw, i didn't expected that a name could have such effect. If developers don't like Service Fabric, that is a different subject. First, SFM is a brand of SF, it's the managed version of SF, so it's tied to it. Second, SF is being Open-Sourced, so the Argument of Proprietary is no longer valid. Third, anyone will see that SFM will use the same terms than SF (app, service, replica, partition...), We will see even shared documentation, so soon or later we will discover it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fservice-fabric-mesh-preview-pr%2Fissues%2F206%23issuecomment-403375923&data=02%7C01%7CChackDan%40microsoft.com%7C9b7e2b2ced344d7ad0d708d5e56759a9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636667154410570027&sdata=YTljP4M%2B6Fw9Vao1Jhcws87BniSjkYy73o7xczxcGMk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKq9pmWeTv3b9pPrvKXXyCpPDpSMYOllks5uEvuugaJpZM4VGrCJ&data=02%7C01%7CChackDan%40microsoft.com%7C9b7e2b2ced344d7ad0d708d5e56759a9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636667154410570027&sdata=GV15TYbd9WYEVaJ9zBMDe3izd6j35PFqYzbPtbFo5fQ%3D&reserved=0.