Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By : Gabriel Baptista, Francesco Abbruzzese
Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By: Gabriel Baptista, Francesco Abbruzzese

Overview of this book

Software architecture is the practice of implementing structures and systems that streamline the software development process and improve the quality of an app. This fully revised and expanded second edition, featuring the latest features of .NET 5 and C# 9, enables you to acquire the key skills, knowledge, and best practices required to become an effective software architect. This second edition features additional explanation of the principles of Software architecture, including new chapters on Azure Service Fabric, Kubernetes, and Blazor. It also includes more discussion on security, microservices, and DevOps, including GitHub deployments for the software development cycle. You will begin by understanding how to transform user requirements into architectural needs and exploring the differences between functional and non-functional requirements. Next, you will explore how to carefully choose a cloud solution for your infrastructure, along with the factors that will help you manage your app in a cloud-based environment. Finally, you will discover software design patterns and various software approaches that will allow you to solve common problems faced during development. By the end of this book, you will be able to build and deliver highly scalable enterprise-ready apps that meet your organization’s business requirements.

Related Content you might be interested in

Current Title:

Small book image
Software Architecture with C# 9 and .NET 5 - Second Edition
Gabriel Baptista | Francesco Abbruzzese
Dec, 2020 | 700 pages
Small book image
Microservices with Azure
Rahul Rai | Namit Tanasseri
Jun, 2017 | 360 pages
Small book image
Enterprise Application Development with C# 9 and .NET 5
Arun Kumar Tamirisa | Ravindra Akella | Suneel Kumar Kunani | Bhupesh Guptha Muthiyalu
Mar, 2021 | 610 pages
Small book image
Modern Web Development with ASP.NET Core 3
Ricardo Peres
Jun, 2020 | 802 pages
Table of Contents (26 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
1
Understanding the Importance of Software Architecture
Understanding the Importance of Software Architecture
What is software architecture?
Software development process models
Gathering the right information to design high-quality software
Using design techniques as a helpful tool
Common cases where the requirements gathering process impacted system results
Case study – introducing World Wild Travel Club
Summary
Questions
Further reading
Free Chapter
2
Non-Functional Requirements
Non-Functional Requirements
Technical requirements
Enabling scalability, availability, and resiliency with Azure and .NET 5
Performance issues that need to be considered when programming in C#
Usability – why inserting data takes too much time
The fantastic world of interoperability with .NET Core
Achieving security by design
Book use case – understanding the main types of .NET Core projects
Summary
Questions
Further reading
3
Documenting Requirements with Azure DevOps
Documenting Requirements with Azure DevOps
Technical requirements
Introducing Azure DevOps
Organizing your work using Azure DevOps
Managing system requirements in Azure DevOps
Use case – presenting use cases in Azure DevOps
Summary
Questions
Further reading
4
Deciding the Best Cloud-Based Solution
Deciding the Best Cloud-Based Solution
Technical requirements
Different software deployment models
Why are hybrid applications so useful in many cases?
Book use case – which is the best cloud solution?
Summary
Questions
Further reading
5
Applying a Microservice Architecture to Your Enterprise Application
Applying a Microservice Architecture to Your Enterprise Application
Technical requirements
What are microservices?
When do microservices help?
How does .NET deal with microservices?
Which tools are needed to manage microservices?
Summary
Questions
Further reading
6
Azure Service Fabric
Azure Service Fabric
Technical requirements
Defining and configuring your Azure Service Fabric cluster
Use case – Logging microservices
Summary
Questions
Further reading
7
Azure Kubernetes Service
Azure Kubernetes Service
Technical requirements
Kubernetes basics
Interacting with Azure Kubernetes clusters
Advanced Kubernetes concepts
Summary
Questions
Further reading
8
Interacting with Data in C# – Entity Framework Core
Interacting with Data in C# – Entity Framework Core
Technical requirements
Understanding ORM basics
Configuring Entity Framework Core
Entity Framework Core migrations
Querying and updating data with Entity Framework Core
Deploying your data layer
Understanding Entity Framework Core advanced features
Summary
Questions
Further reading
9
How to Choose Your Data Storage in the Cloud
How to Choose Your Data Storage in the Cloud
Technical requirements
Understanding the different repositories for different purposes
Choosing between structured or NoSQL storage
Azure Cosmos DB – an opportunity to manage a multi-continental database
Use case – storing data
Summary
Questions
Further reading
10
Working with Azure Functions
Working with Azure Functions
Technical requirements
Understanding the Azure Functions app
Programming Azure functions using C#
Maintaining Azure functions
Use case – Implementing Azure Functions to send emails
Summary
Questions
Further reading
11
Design Patterns and .NET 5 Implementation
Design Patterns and .NET 5 Implementation
Technical requirements
Understanding design patterns and their purpose
Understanding the available design patterns in .NET 5
Summary
Questions
Further reading
12
Understanding the Different Domains in Software Solutions
Understanding the Different Domains in Software Solutions
Technical requirements
What are software domains?
Understanding domain-driven design
Entities and value objects
Using SOLID principles to map your domains
Aggregates
The repository and Unit of Work patterns
DDD entities and Entity Framework Core
Command Query Responsibility Segregation (CQRS) pattern
Command handlers and domain events
Event sourcing
Use case – understanding the domains of the use case
Summary
Questions
Further reading
13
Implementing Code Reusability in C# 9
Implementing Code Reusability in C# 9
Technical requirements
Understanding the principles of code reusability
Reusability in the development life cycle
Using .NET 5 or .NET Standard for code reuse
How does C# deal with code reuse?
What if the code is not reusable?
I have my libraries. How do I promote them?
Use case – reusing code as a fast way to deliver good and safe software
Summary
Questions
Further reading
14
Applying Service-Oriented Architectures with .NET Core
Applying Service-Oriented Architectures with .NET Core
Technical requirements
Understanding the principles of the SOA approach
SOAP web services
REST web services
How does .NET 5 deal with SOA?
Use case – exposing WWTravelClub packages
Summary
Questions
Further reading
15
Presenting ASP.NET Core MVC
Presenting ASP.NET Core MVC
Technical requirements
Understanding the presentation layers of web applications
Understanding the ASP.NET Core MVC structure
What is new in the latest versions of ASP.NET Core?
Understanding the connection between ASP.NET Core MVC and design principles
Use case – implementing a web app in ASP.NET Core MVC
Summary
Questions
Further reading
16
Blazor WebAssembly
Blazor WebAssembly
Technical requirements
Blazor WebAssembly architecture
Blazor pages and components
Blazor forms and validation
Blazor advanced features
Third-party tools for Blazor WebAssembly
Use case – implementing a simple application in Blazor WebAssembly
Summary
Questions
Further reading
17
Best Practices in Coding C# 9
Best Practices in Coding C# 9
Technical requirements
The more complex your code, the worse a programmer you are
Using a version control system
Writing safe code in C#
.NET 5 tips and tricks for coding
WWTravelClub – DOs and DON'Ts in writing code
Summary
Questions
Further reading
18
Testing Your Code with Unit Test Cases and TDD
Testing Your Code with Unit Test Cases and TDD
Technical requirements
Understanding unit and integration tests
Understanding test-driven development (TDD)
Defining C# test projects
Use case – Automating unit tests in DevOps Azure
Summary
Questions
Further reading
19
Using Tools to Write Better Code
Using Tools to Write Better Code
Technical requirements
Identifying well-written code
Understanding and applying tools that can evaluate C# code
Applying extension tools to analyze code
Checking the final code after analysis
Use case – Evaluating C# code before publishing an application
Summary
Questions
Further reading
20
Understanding DevOps Principles
Understanding DevOps Principles
Technical requirements
Describing DevOps
Understanding DevOps principles
Understanding continuous delivery with Azure DevOps
Defining continuous feedback and the related DevOps tools
Understanding SaaS
The WWTravelClub project approach
Summary
Questions
Further reading
21
Challenges of Applying CI Scenarios
Challenges of Applying CI Scenarios
Technical requirements
Understanding CI
Continuous Integration and GitHub
Understanding the risks and challenges when using CI
Understanding the WWTravelClub project approach
Summary
Questions
Further reading
22
Automation for Functional Tests
Automation for Functional Tests
Technical requirements
Understanding the purpose of functional tests
Using unit testing tools to automate functional tests in C#
Use case – automating functional tests
Summary
Questions
Further reading
23
Answers
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
Chapter 11
Chapter 12
Chapter 13
Chapter 14
Chapter 15
Chapter 16
Chapter 17
Chapter 18
Chapter 19
Chapter 20
Chapter 21
Chapter 22
24
Another Book You May Enjoy
Another Book You May Enjoy
25
Index
Index

What are software domains?

As we discussed in Chapter 2, Non-Functional Requirements, and Chapter 3, Documenting Requirements with Azure DevOps, the transfer of knowledge from domain experts to the development team plays a fundamental role in software design. Developers try to communicate with experts and describe their solutions in a language that domain experts and stakeholders can understand. However, often, the same word has a different meaning in various parts of an organization, and what appear to be the same conceptual entities have completely different shapes in different contexts.

For instance, in our WWTravelClub use case, the order-payment and packages-handling subsystems use completely different models for customers. Order-payment characterizes a customer by their payment methods and currency, bank accounts, and credit cards, while packages-handling is more concerned with the locations and packages that have been visited and/or purchased in the past, the user&apos...

Previous Section
End of Section 3
Next Section