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. Totally Support Service Mesh in Service Fabric

    Service mesh use SideCar design partten, I think Service Fabric Reserve Porxy is a implement of SideCar design partten.

    But according the article: https://thuru.net/2018/10/18/service-mesh-in-service-fabric-is-inherent/

    "In Service Fabric, control plane is not available as per the complete definition in the above article. Most of the control plane functions are application model specific and implemented by the developers and some are in built in the communication and federation subsystem of Service Fabric. The key missing piece in the control plane component of Service Fabric is, the unified UI to manage the communication infrastructure (or the data plane)."

    There is no control plane…

    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 →
  2. Consider running Windows Update/AV signature update after a node is re-imaged

    We have run into a corner case where node was re-imaged in late September using an image that was created in early September. The node was offer September cumulative update and AV signature was outdated for sometime.

    If a node is re-imaged, it should run everything up-to-date before it is put back in service instead of waiting on other update mechanism to kick in which might take some time.

    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 →
  3. Quick start template using storage account takes 30mins to start up

    The Azure QuickStart template for Sevice Fabric defaults to using regular storage accounts which takes a considerable amount of time to start the VM Scale Set (15 minutes vs. 2 minutes for Managed Disks). This also results in the slow docker pulls of large images (windows server image) because the decompression takes a long time.

    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 →
  4. 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 →
  5. Allow hiding java samples in documentation

    would be great if there was a way to hide C# or Java sample-code in the documentation on docs.microsoft.com, depending on which one you are using.

    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 →
  6. Add support for expandable environmental variables passed to containers

    Need to be able to pass custom dynamic variables into running containers like docker does (https://docs.docker.com/v17.09/compose/environment-variables/) so one can pass for example environmental value existent on docker host

    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 →
  7. Can't see which version of service fabric i'm running

    Service fabric regularly has breaking change versions that can prevent deployment, with NO diagnostics -- the user is just left with the debugger running, no uncaught exceptions, no debug breaks.

    At the very least, there should be an easy way to verify which version of the service fabric runtime I have deployed.

    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 →
  8. 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 →
  9. Network saturation at 10 GB/s caused fabric node to die

    When the network is saturated on the cluster, the cluster main service dies and then Service Fabric management is not available.

    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. Can not move to another subscription

    Since the service fabric has vm scale set, it can not be moved to another subscription. But, according to document service fabric is a resouce that can be moved.

    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 →
  11. UWP client applications need a high-level library for using Service Fabric Reliable Actors (ActorProxy support for UWP clients)

    Azure Service Fabric Reliable Actors seem like a great server-side technology for multi-user applications. Unfortunately, UWP client applications cannot use the use the ActorProxy to call methods in remote actor objects (implementing IActor interfaces) because the Microsoft.ServiceFabric.Actors NuGet package only supports .NET 4.5 -- not the UWP platform.

    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 →
  12. In Service Fabric Explorer, sort all items logically, especially node names.

    In Service Fabric Explorer, sort all items logically, especially node names. For example, nt02 should appear in a list before nt010.

    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 →
  13. Give partitions meaningful names

    Rather than GUIDs in the service tree, show the information for the partition:
    Named partitions - the name f the partition (the most useful case)
    Range partitions - the range
    Singleton - The GUID is fine here.

    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 →
  14. 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 →
  15. Run Service Fabric Mesh at a high container-to-core ratio,

    Is it possible to set it up with a 10:1 container to core ratio?

    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 →
  16. Make node properties Dynamic

    Make node properties Dynamic to prevent service placements on certain nodes temporarily. For instance, prevent service placement of a stateful service on a new node till certain node property is set.

    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 →
  17. 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 →
  18. Disallow cluster certificates as client certificates

    Cluster certificates have two abilities - node-node communication, but also client-node communication.

    It is hard for a cluster owner to see the ramifications of using the cluster cert as a client certificate. Doing such should be disabled by default to follow "secure by default" configuration and then allow it if someone really needs it.

    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 →
  19. Ability to view multiple clusters

    It would be more productive to be able to view multiple clusters in the same application; not opening multiple instances. i.e.: Have a tabbed interface

    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 →
  20. Remove service fabric mesh dependency on Hyper-V

    I've been porting a Service Fabric system to Service Fabric Mesh, and found a small inconvenience, Service Fabric Mesh depends on having Hyper-V installed, which makes it more difficult and costly to develop inside a Virtual Machine, especially Azure -based Development Virutal Machines.

    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 →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base