device-simulation-dotnet/WebService
Hugh Xiong bb62b8f017 Changes to create default simulations (#298) 2018-10-30 00:10:37 -07:00
..
Auth Maintenance and clean up some build warnings (#252) 2018-09-13 10:25:29 -07:00
Properties Changes to create default simulations (#298) 2018-10-30 00:10:37 -07:00
Runtime Changes to create default simulations (#298) 2018-10-30 00:10:37 -07:00
v1 Add ActiveDevices counter to statistics and other updates (#304) 2018-10-29 16:36:27 -07:00
DependencyResolution.cs Integrate SimulationManager (#270) 2018-10-17 17:16:05 -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 Changes to create default simulations (#298) 2018-10-30 00:10:37 -07:00
WebService.csproj Changes to create default simulations (#298) 2018-10-30 00:10:37 -07:00
appsettings.ini Changes to create default simulations (#298) 2018-10-30 00:10:37 -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