You're reading from Solution Architecture with .NET Learn solution architecture principles and design techniques to build modern .NET solutions

Product type Paperback

Published in Aug 2021

Publisher Packt

ISBN-13 9781801075626

Length 238 pages

Edition 1st Edition

Languages

UML

Tools

.NET

Concepts

Solution Architecture

Author (1):

Jamil Hallal

View More author details

Table of Contents (15) Chapters

Preface

1. Section 1: Understanding the Responsibilities of a Solution Architect

2. Chapter 1: Principles of the Software Development Life Cycle FREE CHAPTER

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

Exploring CI/CD with Azure pipelines

Continuous integration, continuous delivery, and continuous deployment (or CI/CD) are the main pillars of building, testing, and deploying robust applications using modern software development techniques in DevOps. These practices allow us to release new features and fixes quickly through automated processes. Let's get to know each of these practices.

Continuous integration (CI) is the nucleus practice in DevOps. It allows us to frequently integrate all source code modifications coming from multiple developers into the main repository. It is an automated process that can be configured in Azure DevOps. When this capability is enabled, every time a developer commits their code, the CI will be verified by starting an automated build process to verify that the project contains no build errors. After that, an automated testing process is triggered to confirm that the newly committed code is stable. This approach is very helpful for identifying...