Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Easily allow publishing the same application twice but listening on different endpoints

    I want to have a Web API lets say in have it listen on https://localhost/Environment1/api/

    Now a completely separate instance of the same application deployed in the same cluster except now Web API is listening on https://localhost/Environment2/api/

    I also want to do this with WCF, and the built in Remoting listeners very easily as well so that I can I have multiple different instances of the same application at the same version running in the same cluster just with different parameters like listeners, etc...

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Join a Domain in a Azure Virtual Network

    To access a share on a Virtual Machine it is required for the Cluter to Join a Domain inside the Virtual Network. Please make it possible to join the cluster to a domain.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow ICommunicationListener to handle multiple endpoints

    Our current services are engineered with a single HttpListener which registers all endpoint prefixes for our service (e.g. http and https). With the current Service Fabric model ICommunicationListener.OpenAsync requires us to return a single endpoint string. This not only imposes a non-trivial refactor upon us, but also seems to be a waste of resources in the service.
    It would be ideal if ICommunicationListener.OpenAsync could return an IEnumerable<string> for multiple endpoints.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Merge AppFabric and ServiceFabric (Again)

    Once, when AppFabric got anounced, it appeared that there were plans to set up a mesh-orientated inter-computer centric ComponentServices snapin replacing Com++ on the long run.
    As such, Service Fabric belongs into AppFabric, althemore, since it brings the successor of MSMQ, which in turn is adminisitratable within COM++.

    I see no reason for two lonely and weak Service Fabric and App Fabric components.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Button to copy the name of application and services with one click

    Button to copy the name of application and services with one click in the service fabric explorer

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow for non HA on premise production deployments

    Right now you can create a virtual dev cluster on one machine or a real cluster on multiple machines. I want to be able to have real production deployments on 1 or 2 machines. I realize I will be losing some of the features by doing this but still a lot of the features are still applicable. This will give me the ability to have a low cost non HA mode to my apps with the ability to easily have a higher cost HA mode. In the non HA mode I will just rely on the same kind of simple…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Service Fabric SDK is MISSING!

    I'm trying to download the SDK for a new dev machine, but all the links to the SDK from this page: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-get-started/ return a 404.

    The installer I downloaded previously no longer works either because it cannot find the content to install. I need this urgently to continue development, please help.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Activity log on the service fabric explorer

    As well as showing the current state the Service Fabric Explorer should show a cluster activity log of say 24 hours including information such as: Start Application X Upgrade, Completed Application X upgrade, Node 1 offline, Node 1 online etc.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Reduce the seemingly random "502, 503, 504" Situations caused by Azure Fabrics

    We regularly get short outages in connectivity with our Azure Websites, WebJobs and even TrafficManger protected domains (we have several handfull of these across west and north Europe). Our systems are stable -- we have verified this in our logs -- but the connectivity simply drops off with "50X errors" to Sites or WebJobs or TrafficManger-Endpoints. This happens across the board (all of our systems) so cannot be attributed to a system failure. I suspect that the Azure "Fabric" causes these frustrating hick-ups. All we can do is wait, and pray, that it will be soon over :-)

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Basics of service fabric

    Please mention terminologies of service fabric, i.e what is cluster nodes actors stateless stateful clearly in proper documentation.It is very difficult for me to understand what's going on when i am coming from monolithic architecture background and have been in azure for few years.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Documentation that shows what the service endpoints are when trying to connect to an app on a service fabric cluster.

    This may seem arbitrary, but I've created a reliable actor app with a ASP.Net Web API endpoint, but I can't figure out how to reach the endpoint once I publish it to my cluster. The documentation seems to assume that I'll know.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Visual Basic Support - Project Templates

    Please provide some guidance on how to use Service Fabric in Visual Basic. A project template would atleast be a good start.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Color Schemes for Service Fabric Explorer to better distinguish environments

    The Service Fabric Explorer web application should have different color schemes to choose from. This way we could assign different color schemes for different environments. This would make it immediately clear when you are working in a production environment and prevent accidental actions.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Essentials/Details view - sticky

    In the SF Explorer most views have an Essentials view and a Details view. If I select Details view then I'd like the Explorer to remember that 'mode' selection for all views. Currently, every resource is shown initially in Essentials view.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support for generic methods

    Support for generic service/actor operations would be a great addition!

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Service Fabric Explorer Refresh Tree View

    The tree view of the Service Fabric Explorer (web version) should refresh under the currently selected node. Or at least provide a refresh button on each tree node.

    The Auto Refresh feature only refreshes the content on the right.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Ability to dynamically add/remove instances as per the Orleans framework Liveness (Reliable)

    Ability to dynamically add/remove instances as per the Orleans framework Liveness (Reliable)

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Remindable API could be much friendlier

    Right now the RegisterReminder and IRemindable interface force the responsibility of serialization onto the person implementing an actor because you must serialize whatever state you want to a byte[] when calling RegisterReminder and then deserialize the state in ReceiveReminderAsync.

    I would propose that RegisterReminderAsync be redone as a generic method where the runtime takes care of serialization under the covers for you and then IRemindable be turned into a generic interface IRemindable<T> that would allow you to receive the instance of T with the runtime once again owning the responsibility of deserializing it for you.

    The benefits are:

    1) Allows…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Immutable Invocation

    When using the Actor model
    calling between actor within the process (not cross node)
    can be dramatically improve for immutable messages
    if the call wont serialize the message (use direct call)

    .NET currently don't support Immutable type enforcement
    but Service Fabric can use attribute on the Actor's method
    which leave it to the developer responsibility (kind of invocation strategy which the developer can choose)
    and when Using Roslyn compiler
    Service Fabric can add Visual Studio Analyzer which cause error
    when trying to use the strategy with non Immutable class.
    C# 6 support immutable property like
    public int Data {get;}

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Establish a (persistent) relationship between Actors

    There are several master/detail type scenarios where it would be helpful to have a one-to-many or many-to-many relationship between stateful actors. In the sample and documentation this kind of relationship is established by storing lists of IDs inside the actor state. This works for tens or hundreds of IDs but when you get to thousands or millions it breaks down.

    It would be very useful to have a first-class mechanism for relating actors together and persisting that relationship (presumably in an underlying reliable collection).

    If such a relationship existed an actor could enumerate all of its related actors. There might…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base