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. Reliable pub-sub framework

    Pub-sub is a common pattern in cloud applications. It would be great to have a reliable implementation of it out of the box.

    1,062 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Actor model communications must implement reliable messaging

    At the moment when using ActorModel you may get duplicate messages sent from the client when client gets communication errors or server failure. That in fact means that in the every actor you have to have a logic that will need to understand if message was processed already ot not. This is a standard problem and must be handled by Fabric insfastructure by implementing "reliable messaging". So the framework should detect if it is a duplicated message that already been delivered & processed or not.

    385 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Packaging System for Applications & Services

    Currently, Fabric apps are folders containing Fabric services, tied together by a manifest and Fabric services are folders containing packages (code, config, data), tied together by another manifest.

    This works alright when apps and services are developed within a company/team and not broadly distributed, but it falls apart when trying to distributed things more broadly.

    For example, what if I wanted to distributed fabric versions of Redis, Elastic Search, or Orleans?

    This proposal is to create a system which lets us package and distribute applications and services similarly to NuGet.

    223 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Simplify Configuration

    Currently to make a single configuration setting use by code that differs between environments I have to:
    A) Add the setting to a configuration section in the Settings.xml (mark as "MustOverride", but you still have to provide a value).

    B) Add a (exactly matching) setting to the configuration override section of the application manifest.

    C) Add a application parameter (with a application global name) to the application manifest. This needs a default value that probably matches the one you already provided in the previous step.

    D) Add the parameter to every single application parameters file that matches the parameter name.…

    140 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable event driven programming

    Allow triggers from Azure resources (Storage, DB, Websites, etc) to execute a micro service or app. Similar to the way AWS Lambda does this (e.g. when a new raw is added or modified on a DB, a new file is added to Azure storage, a website goes down, etc).

    130 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to customize rollout of new versions.

    I want the ability to control how quickly a new versions of services are rolled out and what percent of load gets sent to them.

    For example, I want 10% of the load to hit the new version for 1 hour before it is rolled out to any more nodes.

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Cross Actors/Services Transaction

    Support cross Actors/Services transaction

    92 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Expose low level stateful apis

    Sql azure and DocuDB are built on service fabric but use a lower level api for its stateful IO, please expose those apis for other apps as well

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Don't make me run PowerShell in unrestricted mode

    Today in order to set up a cluster or deploy code to my cluster I need to run PowerShell in unrestricted mode:

    Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force -Scope CurrentUser

    Not only does this make me nervous from a security standpoint, but it also appears to interfere with other things that are running PowerShell scripts. (For example, Application Insights starts throwing errors when attempting to run scripts when starting up a Cloud Service.)

    Is there any way we can get around that requirement? I'd be OK enabling unrestricted mode for setting up the cluster if I could then turn it back to…

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Reliable priority queue

    More reliable collections would be helpful. Especially useful would be a reliable priority queue. While this has multiple applications, the most obvious is to prioritize background tasks that need to be performed. Ideally, it should be possible to update priority queue entries, for example because their priority has increased.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Orchestration tooling for local development and test environments

    One thing I feel lacking from what has been displayed from the current tooling around Azure Service Fabric is a way to orchestrate your services and their dependencies during local development or automated testing.

    The two primary situations (for my own use-case at least) would be:


    • I'm a developer that needs to do some changes in Service Fabric application "Application1". A service within this application calls upon an actor or a service "fabric:/Application2/MyServiceOrActor". If I check out "Application1", perform the changes and deploy it locally to test them, it will fail unless I also know before hand about the dependency…
    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add ability to turn off entire cluster.

    In testing scenarios i would like to be able to turn off and delete the entire cluster from Azure portal.

    8 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 →
  13. The cluster is stuck in "deploying" state

    Cluster is stuck in "deploying" state. There is no way to stop it or delete it. Explorer shows nothing.

    5 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 →

    We will need more information inculding traces to diagnose any possible issue here. Is it at the time of creating the cluster, or deploying an application? Can you try resetting the cluster by right-clicking the service fabric explorer taskbar icon?

    Mani Ramaswamy
    Microsoft

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

Service Fabric

Categories

Feedback and Knowledge Base