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. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Out of box support for F#

    I would like to get out of box support for Actor/Services in F#.

    71 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 →
  4. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support for generic methods

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

    5 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 →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Get Reliable Collection from Actor

    Get Reliable Collection from Actor

    having access to reliable collection from Actors (or anywhere)
    can be useful

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. 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 →
  14. Singleton actor-like compute units

    I can see a use for both stateful and stateless units of business logic that are similar to actors, but singletons. I'll call these Units. These would be accessible to clients, Actors and other Units and would be used in a similar way. Some simple examples:

    Stateless:
    var dateProvider = UnitProxy.Create<DateProviderUnit>();
    var date = dateProvider.NowAsync();

    Stateful:
    var idProvider = UnitProxy.Create<IdProviderUnit>();
    var id = idProvider.NextAsync();

    This can be emulated at the moment by using Actors, and using Create with a known ActorId to access the same instance.

    The benefit of making them a 'first class citizen' is that the code would…

    18 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. 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 →
  16. Enable a cross-platform development story (along with publishing)

    The x-plat story for PaaS is a huge help for adoption (Win/OSX/Linux). Most other dev stories are getting this attention in the MSFT space; seems a shame not to enable creation of first-class cloud systems along with the next killer mobile/web app.

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

Service Fabric

Categories

Feedback and Knowledge Base