Whenever I think about a microservices eco in an ASP.NET Core system I think about various small APIs, async programming, callbacks, event triggering, and so on. Actually, the ecosystem is much bigger and somehow more complex.
We have already discussed that the microservice architectural style is a way to create small and independent units of a big application. This is not possible without the use of various tools and utilities.
The following diagram is a pictorial overview of a typical microservices architectural style that depicts different client requests to various services and how this request validates:
A typical microservice ecosystem consists of the following components, you will get an idea about these components in ASP.NET Core in the sections ahead.
