I have a scenario of huge number of asp.net web api in a Microservice architecture. I need to keep all services down till it's going to access by at least one client.
If a client is trying to access an API method and hosted web api service isn't up,
we need to make it up dynamically
Below is may high level plan.
Host all my web api inside different console applications as self host
Inside IIS, there would be wrapper web api service which will be exposed and called by any client.
This wrapper service always up and will internally try to up the console application host accordingly based on getting a client hit.
Is there any other better methods to suggest?