In this tutorial, you will get a basic idea of angular architecture and how the front-end & back-end work together to build a real-time client application. In the previous article, I have explained what is Angular, why you should learn it, and the benefits of using Angular.
Angular Application Architecture
I love modern applications that have at least two parts a front end and backend. The front end also called the client; is the part that runs in the web browser and this is what the user sees and interacts with. So it essentially includes the user interface. For an application, we use Html, CSS, Typescript, and Angular to build the front end.
The back end sits on a web server or multiple web servers in the cloud and it is responsible for storing the data and doing any kind of processing. Our front end or the client app talks to the backend to get or save the data. So here we often have one or more databases as well as a bunch of HTTP services or API to make this data available to the clients.
In case you don’t know API stands for Application Programming Interface. These HTTP services or API are essentially endpoints that are accessible via the HTTP protocol. So we can call them using simple HTTP requests to get or to save the data. You can learn How to create Web API in ASP.NET.
So this is how the big picture works. Refer to read more about Angular concepts.
In the next article, you will learn how to set up your development environment and create your angular project.
I hope you liked this article on angular architecture. I would like to have feedback from my blog readers. Your valuable feedback, question, or comments about this article are always welcome.