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.
Table of Contents (26 chapters)
24
Another Book You May Enjoy
25
Index

Questions

  1. Can services use cookie-based sessions?
  2. Is it good practice to implement a service with a custom communication protocol? Why or why not?
  3. Can a POST request to a REST service cause a deletion?
  4. How many dot-separated parts are contained in a JWT bearer token?
  5. By default, where are the complex type parameters of a REST service's action methods taken from?
  6. How is a controller declared as a REST service? 
  7. What are the main documentation attributes of ASP.NET Core services?
  8. How are ASP.NET Core REST service routing rules declared?
  9. How should a proxy be declared so that we can take advantage of .NET Core's HttpClientFactory class features?