Book Image

Solution Architecture with .NET

By : Jamil Hallal
Book Image

Solution Architecture with .NET

By: Jamil Hallal

Overview of this book

Understanding solution architecture is a must to build and integrate robust systems to meet your client’s needs. This makes it crucial for a professional .NET software engineer to learn the key skills of a .NET solution architect to create a unique digital journey and build solutions for a wide range of industries, from strategy and design to implementation. With this handbook, developers working with the .NET technology will be able to put their knowledge to work. The book takes a hands-on approach to help you become an effective solution architect. You’ll start by learning the principles of the software development life cycle (SDLC), the roles and responsibilities of a .NET solution architect, and what makes a great .NET solution architect. As you make progress through the chapters, you’ll understand the principles of solution architecture and how to design a solution, and explore designing layers and microservices. You'll complete your learning journey by uncovering modern design patterns and techniques for designing and building digital solutions. By the end of this book, you'll have learned how to architect your modern web solutions with ASP.NET Core and Microsoft Azure and be ready to automate your development life cycle with Azure DevOps.
Table of Contents (15 chapters)
Section 1: Understanding the Responsibilities of a Solution Architect
Section 2: Designing a Solution Architecture
Section 3: Architecting Modern Web Solutions with DevOps Solutions

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...