The basic structure looks like this:

Pretty frequent architecture; client sends a request to the API Gateway, it decides where the request will proceed. Assuming all of our microservices are secured with at least JWT Authorization, Auth Resource provides a new JWT.

Install the dotnet template using:

dotnet new -i ./

Create a new application using:

dotnet new mlhub -n Application

API Gateway is implemented using Ocelot. Ocelot makes it very simple to map microservices to specific routes using a json configuration file (in this case ocelot.json).

This application runs locally on http://localhost:6100 and, when using docker-compose, will run locally on http://localhost:5100

Auth Resource is a simple REST Service that provides us with JWT (JSON Web Token) which we must propagate through ours microservices in order to pass the security gates.

In this case, there is a util class called JwtGenerator with method called Generate which takes two arguments; username (for JWT sub Claim) and role name. Role name is essential since we want to guard our endpoints in microservices with [Authorize(Roles = "ROLE_NAME")].

JWT is set to expire in 24 hours.

You can change all JWT Claims and properties in Generate method, mentioned above.

The dotnet microservice template is best used with the application mlhub structure. The mlhub contains all dependency paths as well as an API Gateway for microservices placed in the 'Services' directory. Docker-compose is used to spin up, microservices, databases, and the API Gateway.

Communication between microservices can be both async and sync. Synchronous (REST) communication is yet to be implemented in near future, though asynchronous (RabbitMQ) will be when it becomes necessary.