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. Expose Config folder path for Guest executables

    When deploying a guest executable, it would be great to be able to get the config folder as a variable or something that we can then pass on.

    Currently, you either have to parse the folders to find the config folder, or put the config files needed in the code package folder.

    11 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 →
  2. service fabric shutdown + start option

    Can we have shutdown/ stop option for service fabric to save cost if you have dev/test cluster and want to use once in month,

    We do have alternatives like deleting and recreating cluster of stopping vmss but this are not easy options.

    4 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 →
  3. Move IService and related remoting interfaces to their own namespace

    Please move IService and the related remoting interfaces into their own package/namespace so that you can reference just those and not be coupled to the entire set of service fabric libraries

    It is disappointing that in order to use remoting any service must ultimately inherit from IService. This means you are then coupled to not only the IService interface but ultimately the entire Service Fabric set of namespaces as IService resides in Microsoft.ServiceFabric.Services.Remoting, which of course is dependent on the other packages as well.

    As discussed here https://github.com/Azure/service-fabric-issues/issues/55#issuecomment-276725104

    131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support KeyVault in separate subscription to cluster

    Currently the KeyVault containing the certificate used by the cluster has to be in the same subscription. If not you get the error:
    The SubscriptionId: "x" of the request must match the SubscriptionId "y" contained in the Key Vault Id.
    Forcing both to be in the same subscription makes it difficult to allow a user to have full permissions within a subscription while not giving them direct access to the certificate's private key

    32 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. Ability to stop/disable services without removing them

    Right now, as soon as a service gets deployed to Service Fabric, it will start immediately and the only way to stop it is to completely remove the service. In case of a stateful service, this would also remove the data.

    However, there are scenarios, where stopping/deactivating a service - without removing it - is important:


    • Troubleshooting: If the service is not behaving correctly, we might want to stop it. (it's not always possible to do a rollback)


    • Scheduled services, which should not run all the time


    • Planned downtime: Although against the idea of Service Fabric, there might be scenarios…

    982 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Option to disable service/app deletion confirmation on local/test clusters

    It would be useful to be able to disable confirmations for deleting/unprovisioning when doing local development. it could just be an option in the cluster

    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 →
  7. 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 →
  8. Support for the change in address space of the service fabric cluster VNet.

    Sometime we need to move the existing SF cluster to new address space (say because of overlapping for the future VNets). VMs and Scalesets can be moved to new subnets without much trouble. (add another address space to their current Vnet and create their new subnets in that address space.) However, the Service Fabric Cluster cannot be moved to another address space as the cluster manifest is created with the cluster to point to the scaleset IPs and cannot be changed successfully. Therefore, the cluster has to be redeployed in order to change address ranges, and so all the services…

    6 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. Document How to host multiple HTTPs Apps with different external URLs

    Need Documentation and examples on how to configure and host Multiple .NET Core WebApps using HTTPs Endpoints on a single cluster hosted in Azure.

    Preferably so that externally managed CNAME rules can be applied.

    6 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. "visual studio code"

    Support for Visual Studio Code with tooling on all platforms (windows, mac, linux)

    43 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 →
  11. Support & integration of Eclipse Vert.x for building reactive Java applications on Service Fabric

    Support & integration of Eclipse Vert.x for building reactive Java applications on Service Fabric. First step would be Service Fabric as a Cluster Manager for Vert.x applications

    See: http://vertx.io/docs/#clustering

    2 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. Add Global Exception Handling in SF same way as it is in MVC and Web API

    I was trying to find out how i can handle Exception globally in Service Fabric so i think if we have option to Handle Exception Globally the way way it is in MVC and Web API

    25 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 →
  13. Support scheduled tasks

    Right now, Service Fabric only supports always-running services.

    However, applications also consist of scheduled tasks that execute e.g. daily. Right now, we have to use Azure Batch or the Windows Task Scheduler for this. But managing these tools introduces additional complexity.

    Azure Service Fabric should introduce a "scheduler"-component that supports complex cron-like schedules. When the scheduler starts a service, it should monitor the exe and restart it, if it returns an error code. However, if the exe returns without an error, Service Fabric should see this as a successful execution of the task and wait for the next scheduled execution.

    370 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Portal support for backup and restore

    Azure portal should have an option to backup and restore the Service fabric application and allow to setup timer jobs to take the backups.

    Service fabric features are good if we add this feature also there wont be any issue for maintenance in future of these type of applications

    41 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. consider supporting service fabric on nano server

    having the ability to run azure service fabric on nano server should have a lot of advantages. the smaller footprint of nano-server should allow smaller servers per node, but also leave more resources of powerfull servers for the application that are'nt required for the OS. further by design nano-server would have fewer attack-surface for attackers and require fewer updates that require a node to reboot. i understand the issues that currently prevent service fabric from running on nano-server, like the need for full dotnet-framework. but please keep considering this as a future-option :)

    44 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. Provide extensibility points for Service Fabric Remoting

    The service fabric remoting library is great, though not very extensible.

    I have two immediate needs to satisfy before I can migrate to using the service fabric.


    • Pass a custom header context. This is readily available by inheriting from the ServiceRemotingDispatcher alongside creating an implementation of IServiceRemotingClient.


    • Provide a custom data contract serializer / resolver. I cannot find any way to do this outside of completely writing my own transport.


    In digging through the service fabric remoting code I am discovering that most everything is marked internal and the code is so heavily coupled to internal classes that almost nothing…

    86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 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. 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 →
  19. Client Certificate Authentication

    I have a Web API which has to be hosted in Service Fabric Cluster and it should support Basic Authentication and Client Certificate Authentication (Two way SSL)

    220 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base