Service Fabric

Do you have an idea, suggestion, or feedback based on your experience with Azure Service Fabric? We would love to hear from you.

Please take a few minutes to submit your feedback in one of the forums available on the right or vote up an idea submitted by another Azure Service Fabric customer. All the feedback shared in these forums are being monitored and reviewed by the Microsoft Azure Service Fabric team.

Please remember this forum is for Azure Service Fabric, and if you have feedback on other Microsoft products, services or platforms, please submit your feedback in the appropriate forum (found on the right hand side).

Thanks for your feedback – we look forward to improving your satisfaction with Azure Service Fabric

  1. Add service management options to fabric explorer

    The current context options in the SF Explorer allows deployment and deletion of Application and Services, as well as manage Nodes (pause, restart...)

    I would like the option to control the deployed services more explicitly like restarting a service and be able to start and stop them (without SF trying to restart them). This would be very usefull during development.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make available in UK regions

    Now that we've got UK West and UK South regions, when can we expect to see Service Fabric made available there? As it stands I'm going to have to stick with North & West Europe for my service.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. FabActUtil.exe needs to give failure messages

    By far the single most frustrating part of Service Fabric development is FabActUtil.exe returning -1 for every single solitary error at compile time. It gives no indication whatsoever of what went wrong.

    We have burned extensive hours (and even examined the EXE's code with Reflector) just to try to get the slightest hint of what has gone wrong.

    Sometimes it works locally but fails on the build server. Sometimes it works on one dev's machine and not another. Sometimes it fails on compile and then when immediately recompiling it works.

    Often, we figure out what is causing the failure and…

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Remoting Communication with Node.JS

    It should be possible to run a service on Node.JS which can communicate with C# services using the remoting communication channel. It should be possible to do both-way communication and a ServiceProxy implementation for Node.JS that allows for easy service URI discovery.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Python SDK & Samples

    Support for Python within the templates would be phenominal.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow to choose a folder when adding a new service fabric service

    Please consider to extend the "Add New Service Fabric Service" dialog in visual studio with the option to choose a target folder.

    While the "add New Project" dialog has this ability for good reasons, the add-new-service-fabric-service lacks this setting.
    i guess the desire to not only structure projects in project-explorer, but also structure projects on the file-system-level in a meaningful way is understandable. we want to have all service-fabric-service-projects grouped in a folder below the solution-folder.

    now our problem is, when adding another service-fabric-service to this service-fabric-project, we can not choose in which subfolder it should be created, but instead…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow deployment to Existing VNET in the azure portal

    When setting up a new Service Fabric I should be able to deploy this to an existing VNET from the Azure portal. This is possible today using an ARM Template, but it requires you to modify existing templates. This feature is useful whenever you have hybrid scenarios and you want for instance a stateless service access on-premise data.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. ServiceFabric OData

    Allow access to ServiceFabric metrics & configuration data via an odata API

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add support for JSON config

    I would like to use an easier to read format for ApplicationManifest, ApplicationParameters, and PublishProfiles config files. Ideally as JSON or YAML (see YAML suggestion for voting).

    For JSON, see attached files for proposed format.

    Proposed structure changes:
    In ApplicationManifest.json, I was able to take advantage of json's schemaless notation to reduce a level of nesting by using "ServiceFabricServiceType": "Stateful". If necessary this could be represented more similarly to the current XML format.

    In ApplicationParameters.Cloud.json, I made the parameters key/value pairs rather than complex objects. Again, this could be reverted if needed.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Improve performance of certificate changes

    Changing cluster certificate or simply adding a new certificate seems to take a lot longer than it should even on a cluster or 5 nodes. Usually taking around an hour or more.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Proved equivalent of Spring Cloud Dataflow

    Enable the ability to easily compose simple applications together into a pipeline and to allow scaling those apps independently. Also, allow using kafka as a way to communicate between applications. See Spring Cloud Dataflow.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Prevent accidental deletion of application in Service Fabric Explorer

    Prevent accidental deletion of application in Service Fabric Explorer following the Resource Locks concept in Azure to prevent accidental deletion. (https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-lock-resources)

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow service InitializationData to be set in ApplicationManifest

    If you'd like two instances of the same service type, but with different configuration data, there's no easy way to deploy it via the ApplicationManifest. It would be great if you could specify in the ApplicationManifest a service's InitializationData, just as you can if you're creating the service dynamically via ServiceManager.CreateService.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support messaging communication listener

    Communication via synchron protocols like HTTP and RPC is not resilient. Support for asynchronous messaging would fill the gap. Messages could be stored in stateful services. Also it should be possible to plugin different messaging systems and tools, e.g. NServiceBus. Particular already started implementing some of it, but it's no Service Fabric 100% native solution and beta - See https://docs.particular.net/nservicebus/hosting/service-fabric-hosting/

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Restart service/partition/replica action in explorer

    Similar to delete service action, add restart action to service or partition or replica as appropriate

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add support for YAML config

    I would like to use an easier to read format for ApplicationManifest, ApplicationParameters, and PublishProfiles config files. Ideally as YAML or JSON (see JSON suggestion for voting).

    For YAML, see attached files for proposed format.

    Proposed structure changes:
    In ApplicationManifest.yml, I was able to take advantage of json's schemaless notation to reduce a level of nesting by using "ServiceFabricServiceType": "Stateful". If necessary this could be represented more similarly to the current XML format.

    In ApplicationParameters.Cloud.yml, I made the parameters key/value pairs rather than complex objects. Again, this could be reverted if needed.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a consistent migration path for existing .Net non-cloud applications and developers

    A lot of application that are currently deployed as N-Tier .Net applications use Winforms/WPF on the front end with WebApi or WCF Middle Tiers and Sql Server as the back end. A tutorial of how to migrate those kind of applications to Service Fabric would be great.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add Service fabric Application with ssl endpoint support

    we required to provide SSL endpoints to the fabric for running fabric on SSL port.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add release configuration setting when publishing

    When you publish an application from visual studio you can't specify the release configuration (Debug/Release) to be used and instead it uses the currently active one in visual studio.

    It would be very much appreciated if it was possible to be able to specify which release configuration is desired as part of the publish profile so that you could readily ensure that you publish a debug build to a staging environment and a release build to a production environment.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base