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

Exploring the key principles of solution architecture

Architecture principles outline the fundamental procedures and guidelines that are required to design, build, and deploy a successful software solution. They are meant to influence your architecture approach and improve the quality attributes of the solution.

There are many principles out there that we can adopt in our methodology of work to prepare the design architecture. We can even define our own principles if we think they will add value to the architecture design or if we think they will efficiently improve the design process. Most importantly, we need to make sure we offer a good balance between theory and practice and that we adopt practical and powerful principles that will drive the business and technical changes in our solution's architectures.

In general, we should aim for between 10 and 20 guiding principles for our solution architecture practices. Make sure that you do not have too many principles. This...