Re:C#88: The Original C# (2018)
by JamesBarney on Monday April 01, 2019 @05:10PM
(#19548264)
Sure but most of the gains for microservices are splitting up large teams into independent teams responsible for sub modules which is much larger scale than most C# applications.
Re:C#88: The Original C# (2018)
by scarface74 on Monday April 01, 2019 @06:13PM
(#19548861)
The other benefit of separating functionality into microservices [1], is that it keeps developers from stepping on each other’s toes and merge conflicts. It also lets you scale independently [2].
[1] again I’m not referring to starting out with out of process microservices. They can very well be logically separated within a monolith and using class access modifiers as appropriate.
[2] if you have clean namespace boundaries within your monolith, you program against interfaces instead of classes, and you use a DI framework. Pulling out an assembly/“service” from a monolith becomes a mechanical exercise.
If you need to share a module between teams, it’s easy to package it up as a versioned Nuget package. If you need to separate it out into its own http based microservice. It’s easy to put a Controller on top of it and create an auto generated proxy class if you are describing the API with Swagger.
On the client side, have the proxy class implement the interface.
Of course all this is made easier if you are using a DI framework.