My current web app provides a service to clients on a single site. It is NOT eBay, but I will explain using eBay as an analagous service we can all understand.
A client sets up a page, and other peer users can go to the page, do business, and the site charges for the service, the trades done.
Currently my site is monolithic so does not scale well. All users sit on the same site, and run on the same database, pages hosted in site.
With a redesign for AspNetCore on the cards, I would like to design in some scalability.
I would like to make the selling page in the above example a "site", ie a distinct web application, and fire up such a web application on demand.
Identity Authentication and Authorization will be handled by a stand alone singleton server, issuing tokens (if you like, authenticating against Facebook instead, etc).
A selling client approaches a minimalist central site to set up a selling "page". The selling page, and associated database and app mechanics pertaining to that page are all hosted in a single web-app, which is run on an an elastic resource host (virtual server or docker instance). The page lifetime would be multiple days. The central site runs continuously.
AspNetCore is attractive because the "selling page" site becomes an exe that is spun up on demand.
I am not sure how to make the central site spawn the selling page site on demand. Ideally I would like to avoid marrying a service supplier like AWS or Azure. Would Docker make the app service agnostic? Am I even barking up the right tree?