---

Some Book Contents

Introduction to Containers and Docker

• What is Docker?
• Comparing Docker containers with virtual machines
• A simple analogy
• Docker terminology
• Docker containers, images, and registries

Choosing Between .NET and .NET Framework for Docker Containers

• General guidance
• When to choose .NET for Docker containers
  • Developing and deploying cross platform
  • Using containers for new (“green-field”) projects
  • Create and deploy microservices on containers
  • Deploying high density in scalable systems
• When to choose .NET Framework for Docker containers
  • Migrating existing applications directly to a Windows Server container
  • Using third-party .NET libraries or NuGet packages not available for .NET 7
  • Using .NET technologies not available for .NET 7
  • Using a platform or API that doesn’t support .NET 7
  • Porting existing ASP.NET application to .NET 7
• Decision table: .NET implementations to use for Docker
• What OS to target with .NET containers
• Official .NET Docker images
• .NET and Docker image optimizations for development versus production

Architecting Container and Microservice-Based Applications

• Container design principles
• Containerizing monolithic applications
• Deploying a monolithic application as a container
• Publishing a single-container-based application to Azure App Service
• Manage state and data in Docker applications
• Service-oriented architecture
• Microservices architecture
• Additional resources
• Data sovereignty per microservice
• The relationship between microservices and the Bounded Context pattern
• Logical architecture versus physical architecture
• Challenges and solutions for distributed data management
  • Challenge #1: How to define the boundaries of each microservice
  • Challenge #2: How to create queries that retrieve data from several microservices
  • Challenge #3: How to achieve consistency across multiple microservices
  • Challenge #4: How to design communication across microservice boundaries
• Additional resources
• Identify domain-model boundaries for each microservice

API Gateway Pattern vs. Direct Client-to-Microservice Communication

• Direct client-to-microservice communication
• Why consider API Gateways instead of direct communication
• What is the API Gateway pattern?
• Main features in the API Gateway pattern
• Using products with API Gateway features
• Drawbacks of the API Gateway pattern
• Additional resources

Communication in a Microservice Architecture

• Communication types
• Asynchronous microservice integration enforces autonomy
• Communication styles
• Asynchronous message-based communication
  • Single-receiver message-based communication
  • Multiple-receivers message-based communication
  • Asynchronous event-driven communication
• A note about messaging technologies for production systems
• Resiliently publishing to the event bus
• Additional resources

Creating, Evolving, and Versioning Microservice APIs and Contracts

• Additional resources

Microservices Addressability and the Service Registry

• Additional resources

Creating Composite UI Based on Microservices

• Additional resources

Resiliency and High Availability in Microservices

• Health management and diagnostics in microservices
• Additional resources

Orchestrate Microservices and Multi-Container Applications for High Scalability and Availability

• Software platforms for container clustering, orchestration, and scheduling
• Using container-based orchestrators in Microsoft Azure
• Using Azure Kubernetes Service
• Development environment for Kubernetes

Book Overview

This book dives deep into the principles of microservices. It explains how to design, build, and deploy .NET applications using microservices architecture. The authors break down complex concepts into digestible parts. They cover essential topics such as container orchestration, service discovery, and API management. The book also explores real-world scenarios, providing readers with hands-on examples. Readers will learn how to leverage Docker and Kubernetes for containerization. Furthermore, the authors discuss best practices for monitoring and securing microservices. This comprehensive guide equips developers with the knowledge to create robust, scalable applications.

Why Read This Book

This book is valuable for several reasons. First, it provides a clear understanding of microservices architecture. It helps developers grasp the benefits of using microservices over monolithic applications. Second, the practical examples enhance learning. Readers can apply concepts directly to their projects. Third, the book addresses common challenges in microservices development. It offers solutions that save time and effort. Overall, it serves as a roadmap for modern application development.

Who This Book Is For

This book is ideal for software developers and architects. It suits those who have a basic understanding of .NET. However, it also benefits experienced professionals looking to refine their skills. Project managers and technical leads will find value in its insights. Anyone interested in containerized applications will gain knowledge from this book. It caters to a wide audience, making it a versatile resource.

What You Will Learn

• How to design microservices for scalability and maintainability.
• Best practices for deploying .NET applications using Docker and Kubernetes.
• Techniques for monitoring and securing microservices effectively.

Report Broken Link

File Copyright Claim