I run a two-sided platform with small businesses on one side, and users on another. As a part of our product I plan to introduce "websites" as part of the product.
Idea is: a local business has a domain, and then I want to "turn that into a website" based on one of our templates.
Today we have a .NET application (ASP.NET MVC) running on an Azure web app. We also have a fine API that runs.
This is based on top of a standard SQL database (hosted in Azure).
Imagine you have 100 customers (low traffic websites), and you have 100 custom domains (.com).
We want to give these 100 customers "the same" default website but with their own texts. These texts come from our API.
How would you architect and make this setup? Would you spin up 100 web apps? Run bigger pools in same web app? How would you map the domain to the correct web app?
My proposed solution
Being a bit clueless I am thinking this approach:
Make a new .NET application running as a single instance web-app. Then I would point their DNS (A-record) towards my application, and then somehow look at the current domain (example). Based on the domain, I would get the data based on the API.
Then I would probably make a new web app when this one starts to hit performance problems.
Does my solution make sense? Am I insane? Would this break?
(Answers with links to article(s) or even a book is of course a fine answer!).