In this post, we are going to lớn cover the main benefits of adopting an SPA Architecture while building our Angular Applications, và answer some very comtháng questions regarding SPAs in general.

Bạn đang xem: An spa

This post is part of the ongoing Angular for Beginners series, here is the complete series:

Why the SPA Architecture?

Let’s start with the first question: Why Single Page Applications (SPAs)? This type of applications have sầu been around for years, but they have not yet become widespread in the public Internet.

And why is that?

There is both a good reason for that & an even better reason on why that could change in the near future.

Xem thêm: Tin Tức Triệu Lệ Dĩnh Và Trần Vỹ Đình Hẹn Hò Với Phùng Thiệu Phong

SPAs did get adopted a lot over the last few years for building the private dashboard part of SaaS (Software as a Service) platforms or Internet services in general, as well as for building enterprise data-driven và form-intensive sầu applications.

But does Angular then enforce building our applications as a SPAs?

The answer is no, it does not, but that is an interesting possibility that it brings, given the many benefits of building an application that way. Which brings us khổng lồ a key question:

Why Would You Want to lớn Build an Application as a SPA?

This is something that is often taken for granted. Everybody toàn thân is building applications this way, but what is the big advantage of that? There have sầu lớn be at least a couple of killer features, right?

Let’s start with a feature that does not get mentioned very often: Production Deployment.

Understanding the advantages of SPA use in production will actually also answer the key question:

What is a Single Page Application?

Sometimes names in Software Development are not well chosen, và that can lead to a lot of confusion. That is certainly not the case with the term SPA: a single page application literally has only one page !!