Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Solution Architecture with .NET

You're reading from  Solution Architecture with .NET

Product type Book
Published in Aug 2021
Publisher Packt
ISBN-13 9781801075626
Pages 238 pages
Edition 1st Edition
Languages
Author (1):
Jamil Hallal Jamil Hallal
Profile icon Jamil Hallal
Toc

Table of Contents (15) Chapters close

Preface 1. Section 1: Understanding the Responsibilities of a Solution Architect
2. Chapter 1: Principles of the Software Development Life Cycle 3. Chapter 2: Team Roles and Responsibilities 4. Chapter 3: What Makes an Effective Solution Architect? 5. Section 2: Designing a Solution Architecture
6. Chapter 4: Designing a Solution Architecture 7. Chapter 5: Exploring Architecture Design Patterns 8. Chapter 6: Architecture Considerations 9. Chapter 7: Securing ASP.NET Web Applications 10. Chapter 8: Testing in Solution Architecture 11. Section 3: Architecting Modern Web Solutions with DevOps Solutions
12. Chapter 9: Architecting Modern Web Solutions with ASP.NET Core and Azure 13. Chapter 10: Designing and Implementing Microsoft DevOps Solutions 14. Other Books You May Enjoy

Choosing between traditional web apps and single-page apps

So far, we have seen that there are two approaches to building web applications. One approach is the traditional way, where all the application logic is served on the server side. The other one is the modern approach represented by SPAs, where all the user interaction is handled by the browser using a client-side framework that communicates with the web server by consuming a web API. There is also a way to have a hybrid solution by combining the two approaches together in one solution.

The following diagram shows the two approaches. We can see that in the Single Page Application, we have multiple templates that will be rendered in one single page using a client-side framework; also, there is no full-page refresh in this approach. While in the Traditional Web Application, we can see multiple pages that enforce a full refresh of the page when navigating from one page to another:

Figure 9.1: Single-page application versus traditional web application

Figure 9.1: Single...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime