device-simulation-dotnet/WebService
Devis Lucato a7c0b021bf Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00
..
Auth Maintenance and clean up some build warnings (#252) 2018-09-13 10:25:29 -07:00
Properties Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00
Runtime Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00
v1 Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00
DependencyResolution.cs Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00
Program.cs New logger & dependencies upgrade (#232) 2018-08-12 15:36:40 -07:00
README.md Performance improvements (#223) 2018-07-17 16:37:58 -07:00
Startup.cs Add partitions management (#254) 2018-09-17 22:16:21 -07:00
WebService.csproj Add partitions management (#254) 2018-09-17 22:16:21 -07:00
appsettings.ini Create devices bulk import job (#255) 2018-10-01 10:08:31 -07:00

README.md

Web service

ASP.NET Web API and Kestrel

The web service is built on ASP.NET Web API and hosted via Kestrel, i.e. IIS is not strictly required to run the service, although it would be possible if required. More information can be found here:

Guidelines

The web service is the microservice entry point. There might be other entry points if the microservice has some background agent, for instance to run continuous tasks like log aggregation, simulations, watchdogs etc.

The web service takes care of loading the configuration, and injecting it to underlying dependencies, like the service layer. Most of the business logic is encapsulated in the service layer, while the web service has the responsibility of accepting requests and providing responses in the correct format.

Conventions

  • Web service routing is defined by convention, e.g. the name of the controllers defines the supported paths.
  • The microservice configuration is defined in the appsettings.ini file stored in the WebService project