Making .NET Core more friendly to Microservices
I’ve been working on Microservices for quiet some time now, using the dotnet core (mostly 2.2) to build APIs that call each others and would be consumed by front end. Facing a lot of challenges made me look for alternative solutions and ways to enhance the developer experience when building APIs with dotnet.
Example challenges comes in how to do logging from multiple application in a way that accessible, maintainable, searchable. Challenges in finding the root cause of a down time very quickly. Challenges in tracking and analyzing performance bottlenecks. Challenges in configuration management.
Some of the challenges can be solved using existing workarounds, that you just need to be aware that they exist. Some in my opinion should have been the default behavior but strangely are not. Others need some work to be dealt with and may be the opportunity to start a new open source project to solve.
So I decided I will start this series of articles that tackles these challenges one by one. Try to find existing solutions and workarounds. Then try to provide extensions for new solutions. And eventually will try to build a project template that will have all the best practices turned on by default. To give you a kick start in creating your dotnet core microservice.
