Developing large service fabric application

Question

We are developing an application on service fabric and it is getting larger with time, more code and more service types. Each developer of the team uses local cluster to develop and debug.

The problem is that the build time + local deployment time gets around 15 minutes sometimes (depends if SF is doing application refresh or not) which is frustrating from a developer perspective.

I want to reduce the build and deploy time. What is the recommended pattern for large applications. Should I consider some kind of build-farm & a remote development cluster ?

Note: We are using 'Refresh Application' debugging mode. This does not resolve the problem as sometimes SF chooses to re-deploy the whole app.

Answer 1

Use 'Refresh Application' as the Application Debug Mode .

I recommend you create multiple small applications that can be deployed and upgraded separately. If you're using SF remoting , the built-in retry logic will allow for some remote downtime.

But instead of doing RPC calls, see if you can use the pub/sub pattern. (See this OSS project). This will allow indefinite remote downtime (decoupling services), without the caller having to wait around for an answer. Note that the downside of this decoupling approach is eventual consistency .