This is an exciting time for Service Fabric. Today we released versions 5.6 of the runtime and 2.6 of the SDK with much anticipated support for Windows Server Containers, making Service Fabric a world-class, production-ready container orchestrator for Windows, with Linux not far behind. You can read more about these new container capabilities on the Azure blog. An update to the Service Fabric Standalone will be released separately at a later time.
We’re also announcing a separate preview release of Service Fabric 5.7 that has support for deploying Docker Compose applications to a Service Fabric cluster. The 5.7 Preview is available now in Azure, and the 5.7 Preview SDK will be available for download in the next few days on Web Platform Installer and NuGet. Note that you won’t be able to upgrade a cluster that is running the 5.7 Preview, neither from an earlier release version, nor from the preview release to the final release when it’s available. For this preview release, we’ve used a special versioning scheme for the Service Fabric runtime that looks like this: 255.255.5709.255, which is what you’ll see when you create a cluster with the 5.7 Preview in Azure:
This same versioning scheme will appear in your installed programs when you install the SDK. The associated preview NuGet packages, however, use the standard 2.7.0-preview versioning scheme you typically see with pre-release NuGet packages.
An update to Visual Studio 2017 tooling for Service Fabric is also available in the Visual Studio 2017 15.3 Preview 1 release, which can be installed side-by-side with the latest stable release of Visual Studio 2017. If you’re still using Visual Studio 2015, we’ve got you covered too with an update to the Service Fabric tools included with the SDK.
Some other highlights of this release include:
New Service Package Activation options
A new exclusive process activation option for service instances creates a dedicated process for each replica of a service. With this new option, you can now choose to use the current shared process hosting model for services instances and replicas, or you can choose to run everything in its own process.
Patch orchestration service
We’ve released an application that you can download and deploy to your cluster to automate OS patching for your cluster nodes. This application ensures OS updates are automatically downloaded and installed, and the node is rebooted when necessary. This application is integrated into the Service Fabric health system for safe, coordinated patch roll-out, and it works in both Azure clusters as well as standalone clusters.
Reliable Concurrent Queue
The Reliable Concurrent Queue replicated data structure, which provides concurrent producer and consumer functionality with best-effort FIFO ordering, is now out of preview and ready for production use.
Many services, especially containerized services, can have an existing DNS name, and being able to resolve these using the standard DNS protocol (rather than the Naming Service protocol) is convenient, especially in application “lift and shift” scenarios. The DNS service provides DNS resolution for service endpoints running in your cluster.
Reverse Proxy improvements
A number of new features and improvements have gone into the Reverse Proxy, including HTTPS forwarding, client certificate authentication, and support for custom user-defined HTTP verbs.
Certificate revocation list management
This new improvements gives you more control over how certificate revocation list settings and how they’re handled by the system to find the right balance between security and availability for your cluster.
As always, be sure to read through the full release notes for a complete list of new features, improvements, and bug fixes.
The Service Fabric Team