Microsoft has been open sourcing a lot of its software, services and even its documentation as of late. But some of the pieces the company is releasing this way are more noteworthy and surprising than others.
Yesterday, March 14, officials blogged that the company is open sourcing Service Fabric. Service Fabric is going open source under the MIT license and "over the coming months" will transition to an open development process on GitHub, the team said.
A quick refresher: Service Fabric (first known as "Windows Fabric" is Microsoft's Azure platform-as-a-service 2.0 microservices platform. Service Fabric also competes to some degree with Kubernetes, as both platforms can act as orchestrators, packaging, deploying and maintaining applications and containers.
Microsoft officials have referred to Service Fabric as its "secret sauce," and use it internally to run pieces of the Azure core, Skype for Business, Intune, Event Hubs, Azure SQL DB Cosmos DB, Cortana and more. Microsoft has made available Service Fabric for Windows and Service Fabric for Linux, as well as Service Fabric on Windows Server and on Linux in Azure. Officials have said in the past plan to make Service Fabric available on non-Microsoft clouds.
Over the past year, Microsoft open sourced various pieces of Service Fabric, including Reliable Services, Reliable Actors and its ASP.NET Core integration libraries. Microsoft's plan is to open source the entire Service Fabric runtime, plus a build environment for Linux and Windows. The company will continue to support all Service Fabric products -- Service Fabric in Azure and all standalone offerings -- even once Service Fabric is on GitHub.
Microsoft plans to continue to maintain control over Service Fabric even as it is open sourced, at least for the time being. From the company's blog post:
The original ACS is being deprecated and retired, officials recently confirmed in Microsoft documentation. (Thanks to Directions on Microsoft's Jim Gaynor for the find.) The plan is to start deprecating ACS "around the time" the Kubernetes version of the service is generally available -- something for which Microsoft has not provided a date. Developers will have 12 months to migrate from the original ACS to the Kubernetes container service, according to the documentation.