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)
1
Section 1: Understanding the Responsibilities of a Solution Architect
5
Section 2: Designing a Solution Architecture
11
Section 3: Architecting Modern Web Solutions with DevOps Solutions

Unified solution for logging and tracing

.NET logging providers are used to log event messages to track the execution of the application and report all code errors or application exceptions in a centralized location. Tracing is used to track and view diagnostic information about a single flow in the system.

Logging and tracing are essential for .NET teams as every time the application fails, we request information to troubleshoot the issue and resolve it. The unified solution for logging and tracing will give you answers to the following questions:

  • Why did the system fail to complete the action?
  • When did the error occur?
  • Which function in the code caused the exception?
  • What was the status of the data exchanged between the functions?

For traditional solutions that are hosted on-premises, logging and tracing are performed by the same process that runs the executable of the application. As for modern cloud applications that are built with the microservices...