Community Round-up: May 2016

Now that Service Fabric has reached GA, we are seeing lots of great activity in the community as developers dig deeper into the product and learn how it can solve problems for them. Whether it's external blog posts sharing best practices, StackOverflow answers covering common troubleshooting procedures, or GitHub projects offering useful extensions to the platform, there's a lot of high quality stuff out there! At the same time, we recognize that it can be difficult to keep up with all of the different channels where content is being distributed. To help with that, we'll regularly pull together links to content from the community into a summary blog post.

Without further ado, here are some of the things that have caught our eye recently:

Speaking of community, we'll be hosting a community Q&A on May 19th at 10am Pacific Time. This will be an open, informal session where you can bring any and all Service Fabric questions to the product team. No RSVP required - simply join the meeting at 10am on the 19th.

That's it for the first community round-up. If you have something you'd like considered for a future post, please tag it with #azureservicefabric on Twitter and we'll take a look!


The Service Fabric Team

Comments (5)
  1. Michael Shmalko says:


    Can you please elaborate on Service Fabric SLA. We are having doubts in SA readiness for production based on the recent incident in Australian datacentre and the fact that there is no SLA for SF service.
    Although the cluster VMs and storage are covered by SLAs, it is not clear how incidents related to SF system upgrades are covered and we would really appreciate some clarity on the SF reliability as a service.

    Thank you,
    Michael Shmalko

  2. Mike-EEE says:

    Hey there… OT… is there an RSS feed for this blog? my is not picking it up…

      1. Mike-EEE says:

        Awesome! Thank you!!!

  3. mikanyg says:

    I have read Gonazalo Ruiz article on using Application Gateway for load-balancing, and I am a bit unsure what purpose this has over the normal Azure Load balancer? I understand the difference between layer 4 and layer 7 LBs, but in case of a service fabric cluster with micro services, does it makes sense to configure an additional application gateway on top of the normal load balancer?

Comments are closed.

Skip to main content