First published on MSDN on Aug 09, 2017
Service Fabric version 5.7 of the runtime and 2.7 of the SDK is now available, packed with new features, improvements, and bug fixes for containers, SDK, Reverse Proxy, and the core system itself.
Some highlights of this release:
Run Reliable Services and Reliable Actors in Windows Containers (Preview)
Reliable Services and Reliable Actors can now be packaged and run in Windows containers. This feature is currently **in preview**, with Visual Studio integration planned for an upcoming release.
Assign unique IP addresses to services and containers with open networking mode
In addition to the default “nat” networking mode, Service Fabric now supports “open” networking mode. This mode allows each Service Fabric service - whether it's in a container or not - to get a dynamically assigned IP. Thus, with this feature, you can have multiple services listening on the same port.
ASP.NET Core 2.0 support
The Microsoft.ServiceFabric.AspNetCore.* NuGet packages now support ASP.NET Core 2.0.
Note that only stable builds of ASP.NET Core 2.0 packages are supported; pre-release/preview builds (for example, v2.0.0-preview2-final) of ASP.NET Core 2.0 are not guaranteed to work properly. A final stable build of ASP.NET Core 2.0 packages should be available on NuGet soon.
Also note that the ASP.NET Core WebListener package has been renamed to HttpSys in ASP.NET Core 2.0. Support in Service Fabric for the new HttpSys package is not available yet in this release, but is coming soon. See the full release notes for more details on this.
A consistent cluster configuration between your local development cluster, standalone clusters, and Azure clusters
The cluster configuration for a local development cluster now uses the same clustersettings.json format that a standalone cluster uses, instead of the older ClusterManifest.xml format. This is also more closely aligned with Resource Manager templates for Azure clusters, which has similar settings to clustersettings.json. This will make it much easier to configure a local development cluster to resemble a production cluster, because the configuration format is identical for standalone clusters and more similar to Azure clusters.
Ability to send urgent health reports to the cluster immediately
You can now send urgent health reports to the cluster immediately without waiting for the usual batch send interval. This is very useful in situations where a process crash is imminent, like during unhandled exceptions, where there isn't time to wait for the next batch send interval.
As always, be sure to read through the
full release notes
for a complete list of new features, improvements, and bug fixes.
See you at our upcoming Service Fabric Community Q&A on August 17th @ 10AM PST. Check back on this blog for more details.