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

Scaling Git for enterprise DevOps

Git is one of the most essential version control systems that is adopted by development teams and companies. Git is a distributed version control system, which means the local copy of the source code that's stored on each machine represents a complete version control repository.

In this section, we will learn more about Git and how to structure repositories, manage branches, and collaborate with pull requests.

Structuring Git repos

There are two types of repositories that we can use with Git:

  • Mono-repo: More than one project is stored in a single repository
  • Multi-repo: Each project has its own repository

Mono versus multi; what's the right approach? There is no direct answer that would recommend a particular approach. The strategy that we choose to use in order to structure our repositories is totally based on our way of managing projects; both types have their advantages and disadvantages. However, it is good...