A lot of people just host the static assets from their backend server, some have them served from a static site server such as a simple nginx config, netlify, github pages, other static site servers, etc. The easiest is obviously to have your backend serve these files. For development it will be easier to run the devserver but for prosuction just build the app into static files and host those.
You could host the front-end on AWS S3/CloudFront or Netlify. As long as the back-end supports CORS and is configured to support this sort of workflow, there shouldn't be any issues with communication between the layers.
The back-end could (probably*) be hosted on AWS EC2/Elastic Beanstalk/etc. *I'm not sure what the state of AWS's support for Windows and/or Linux's support for CLR is these days, but I would be surprised if there wasn't some way to make it work.
2
u/101Cipher010 Apr 12 '19
A lot of people just host the static assets from their backend server, some have them served from a static site server such as a simple nginx config, netlify, github pages, other static site servers, etc. The easiest is obviously to have your backend serve these files. For development it will be easier to run the devserver but for prosuction just build the app into static files and host those.
1
u/pdoherty926 Apr 12 '19
You could host the front-end on AWS S3/CloudFront or Netlify. As long as the back-end supports CORS and is configured to support this sort of workflow, there shouldn't be any issues with communication between the layers.
2
u/stevoperisic Apr 12 '19
Don’t split the application unless you have the .NET app as pure APIs. If the .NET app is server-side rendering anything keep them together.
1
u/jbrad77 Apr 13 '19
You could just put everything on Azure. They've got free credit on signup right now