Well, I can understand the architecture of the Web application?

Question

Angular

Good evening, help me put everything on the shelf in my head. I want to master web development, I had very little experience in working with Asp.Net MVC, now I want to gradually master full-stack, for this I want to write a web application, initially just a blog for myself. The idea is this, I want to try different tools both from the front-end and from the back-end. Do I understand correctly that for this you need to break the application into parts that will be spinning on different servers.
Let's say I want to use Angular2 and Asp.net core (Web API), shouldn't I put it all in one app? Angular2 should be running on its own server (which one?), and the WEB API on another, and then I can safely replace Angular2 with something else and also Asp.net with Python / flask for example?
Perhaps for a simple blog this is too complicated a decision, but it will be just a development for mastering new skills.

Answer 1

You are right - you can start serving Angular files on one port / domain name / ip-address / web server (any web server will do, as long as it can serve static files: IIS / nginx / Apache / built into nodejs), and ASP.NET WebAPI to give on a different port / web server (IIS is required here) - it turns out quite conveniently. Or you can split it by initial paths - for example, give api to URLs starting with "/api/", and Angular files to all others (configured on the web server).
In addition, an ASP.NET WebAPI application can be made "self-hosted", i.e. with a web server built into it, then it can simply be run as a console application, and a separate web server for ASP.NET is no longer needed (but still needed for Angular).

Answer 2

Frontend frameworks are usually assembled by the so-called. assemblers (Gulp, Webpack). The collector produces a set of static files (html, js, css, images, fonts). This static is uploaded to the server and it is issued by the application server (Apach, Nginx).
Sometimes the build is done by the backend. I've seen the Rails gem and PHP solutions.
To start understanding Angular 2, you will have to learn Webpack, Typescript, Javascript, layout (html + css) and only then Angular itself.
You can try something simpler, because Angular 2 has a high entry threshold due to complexity and poor English documentation.