My question is somewhat similar to this question, but the answer doesn't really help me, unless i'm missing something.
If i want to deploy 10+ stateless services (OWIN-based Web API's) into a Service Fabric cluster, well from my understanding of ASF, i would:
- Create a new Service Fabric Application in Visual Studio (call it "MyBackendServices")
- Create 10+ Stateless Web API's
- Add them to the Service Fabric Application
- Deploy to a cluster.
But wouldn't this involve creating all the Web API's in the same Visual Studio solution as the Service Fabric application?
My concern is if we want teams to be fully autonomous, they ideally shouldn't need to share the same Visual Studio solution?
Currently each "team" has their own GitHub repository and Visual Studio solution, and each API gets deployed independently.
I was hoping to port this setup to ASF, where each Web API is it's own solution, and they somehow get packaged into the one Service Fabric application.
Can anyone help me on this?
Thanks