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

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.

Support of RX 3 API
https://github.com/Reactive-Extensions/Rx.NET
can reduce service communication when subscribing to remote query

Actor should be able to subscribe for changes made by other Actors
(like the case with Orleans)
Support Rx API will dramatically improve Complex Event Processing
on multi Actors fabric.

Following the pattern of many other development resources from Microsoft, it would be amazing to see Service Fabric open sourced, so that others can modify, improve and view it.

I was really hoping there would be a low tier option to Develop on for those of us with limited infrastructure. I went to spin up a cluster and start playing today, but the minimum was 5 A1 VMs which would be over $200. Any chance we could get a lower end tier or tone it down to 1 VM to get familiar with the platform with the ability to scale it out?

I noticed ASP.NET 5 applications takes a long time to deploy and debug. About 1-2 minutes on my computer on a brand new project. This should be better optimized to load faster

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.

As the heading states. Support DI frameworks in the programming model.

If I'm going to move some of my core application state from an external state store to reliable collections, I would like to have equivalent tools for inspecting that state apart from the VS debug window.

I would like to be able to create unit tests for the Actors without spinning up a cluster. Something like:

[Setup]
public void Setup(){
ActorTestProxy.Setup<IMyActor>(new MyActorImplementation);
ActorTestProxy.Setup<IMyActorDependency>(new MyActorDependencyMock);
}

[Test]
public async void ActorTest()[
IMyActor actor = ActorTestProxy.Create<IMyActor>(0, "test");
var result = await actor.Foo("hep");
Assert.NotNull(result);
}

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).

Out of the box Azure Service Fabric does not have Stateful Web API service template. I would like to have that.

Here is related stackoverflow question http://stackoverflow.com/questions/37842425/stateful-web-api-service-in-service-fabric-in-vs-2015-update-2

Overall, this framework is amazing, and I love it. However, the one drawback is the turnaround time for slight tweaks. I'd love to have a debug-only hotswap which deployed much faster. Maybe something like: pause the cluster failover monitoring, halt all of the running services for an application, deploy code changes, start them again, and resume failover monitoring.

Support cross Actors/Services transaction

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.

At this moment Azure Service Fabric allow us to deploy a cluster in single region. (Need to specify region)

How we can have multi region deployment so we can failover and performance improvement by deployment to near data-center. Document state that a cluster publish in single data center on deployment so again this is again leads to get system down on something wrong to data center.

Can you please update me if this is your plate to work on and is this feature is coming soon.

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