.NET微服务架构：面向容器化的Microsoft解决方案

需积分: 13 35 浏览量更新于2024-07-09 收藏 13.43MB PDF 举报

"本书《NET-Microservices-Architecture》是.NET Microservices架构指南，由Microsoft Developer Division的.NET和Visual Studio产品团队出版。该书主要关注在容器化环境中的微服务架构设计。" 本书深入探讨了.NET框架下构建微服务架构的关键概念和技术，旨在帮助开发者理解和实践微服务在容器化环境中的应用。微服务架构是一种将大型应用程序分解为一组小型、独立的服务的方法，每个服务都能在其自身的进程中运行，并通过轻量级机制（如HTTP RESTful API）进行通信。这种方式提高了系统的可伸缩性、可靠性和可维护性。书中可能涵盖了以下关键知识点： 1. **微服务概念**：解释微服务的核心理念，包括服务的自治、松耦合、可独立部署以及面向业务能力的划分。 2. **.NET技术栈**：介绍如何利用.NET Core和ASP.NET Core来构建微服务，包括框架的性能优势、跨平台支持和开发工具。 3. **容器化**：详细阐述Docker容器在微服务架构中的角色，包括Docker镜像的创建、容器的管理和编排。 4. **服务发现与负载均衡**：讨论服务如何找到彼此，以及如何实现服务间的负载均衡，例如使用Consul或Eureka等服务发现工具。 5. **数据管理**：涵盖在微服务架构中处理数据库和数据一致性的问题，可能包括事件驱动架构、CQRS（命令查询职责分离）和Saga模式。 6. **API网关**：讲解如何使用API Gateway作为客户端与后端服务之间的接口，集中处理认证、路由和聚合请求。 7. **持续集成/持续部署(CI/CD)**：介绍自动化构建、测试和部署流程，例如Jenkins、Azure DevOps或GitHub Actions的使用。 8. **监控与日志**：讨论微服务架构下的系统监控和日志收集，如Prometheus、Grafana和ELK栈。 9. **安全性**：涉及服务间通信的安全策略，包括OAuth2、JWT（JSON Web Tokens）和SSL/TLS加密。 10. **故障隔离与弹性**：阐述如何设计容错机制，如断路器模式、重试策略和健康检查。本书提供的内容旨在帮助读者理解微服务架构的设计原则，并通过.NET技术实现这些原则，从而在实际项目中构建高可用、可扩展的应用系统。同时，书中还可能包含实例代码和最佳实践，以促进学习和实践。虽然本书基于特定版本的.NET框架，但其中的原理和技术在后续版本中依然具有指导价值。

2 Introduction

What this guide does not cover

This guide does not focus on the application lifecycle, DevOps, CI/CD pipelines, or team work. The

complementary guide Containerized Docker Application Lifecycle with Microsoft Platform and Tools

focuses on that subject. The current guide also does not provide implementation details on Azure

infrastructure, such as information on specific orchestrators.

Additional resources

• Containerized Docker Application Lifecycle with Microsoft Platform and Tools

(downloadable e-book)

https://aka.ms/dockerlifecycleebook

Who should use this guide

We wrote this guide for developers and solution architects who are new to Docker-based application

development and to microservices-based architecture. This guide is for you if you want to learn how

to architect, design, and implement proof-of-concept applications with Microsoft development

technologies (with special focus on .NET Core) and with Docker containers.

You will also find this guide useful if you are a technical decision maker, such as an enterprise

architect, who wants an architecture and technology overview before you decide on what approach to

select for new and modern distributed applications.

How to use this guide

The first part of this guide introduces Docker containers, discusses how to choose between .NET Core

and the .NET Framework as a development framework, and provides an overview of microservices.

This content is for architects and technical decision makers who want an overview but don’t need to

focus on code implementation details.

The second part of the guide starts with the Development process for Docker based applications

section. It focuses on development and microservice patterns for implementing applications using

.NET Core and Docker. This section will be of most interest to developers and architects who want to

focus on code and on patterns and implementation details.

Related microservice and container-based reference application:

eShopOnContainers

The eShopOnContainers application is an open-source reference app for .NET Core and microservices

that is designed to be deployed using Docker containers. The application consists of multiple

subsystems, including several e-store UI front ends (a Web MVC app, a Web SPA, and a native mobile

app). It also includes the back-end microservices and containers for all required server-side

operations.

The purpose of the application is to showcase architectural patterns. IT IS NOT A PRODUCTION-

READY TEMPLATE to start real-world applications. In fact, the application is in a permanent beta

state, as it’s also used to test new potentially interesting technologies as they show up.

5 Introduction to Containers and Docker

Another benefit of containerization is scalability. You can scale out quickly by creating new containers

for short-term tasks. From an application point of view, instantiating an image (creating a container) is

similar to instantiating a process like a service or web app. For reliability, however, when you run

multiple instances of the same image across multiple host servers, you typically want each container

(image instance) to run in a different host server or VM in different fault domains.

In short, containers offer the benefits of isolation, portability, agility, scalability, and control across the

whole application lifecycle workflow. The most important benefit is the environment’s isolation

provided between Dev and Ops.

What is Docker?

Docker is an open-source project for automating the deployment of applications as portable, self-

sufficient containers that can run on the cloud or on-premises. Docker is also a company that

promotes and evolves this technology, working in collaboration with cloud, Linux, and Windows

vendors, including Microsoft.

Figure 2-2. Docker deploys containers at all layers of the hybrid cloud

Docker image containers can run natively on Linux and Windows. However, Windows images can run

only on Windows hosts and Linux images can run on Linux hosts and Windows hosts (using a Hyper-V

Linux VM, so far), where host means a server or a VM.

Developers can use development environments on Windows, Linux, or macOS. On the development

computer, the developer runs a Docker host where Docker images are deployed, including the app

and its dependencies. Developers who work on Linux or on the Mac use a Docker host that is Linux

based, and they can create images only for Linux containers. (Developers working on the Mac can edit

code or run the Docker CLI from macOS, but as of the time of this writing, containers don’t run

directly on macOS.) Developers who work on Windows can create images for either Linux or Windows

Containers.

6 Introduction to Containers and Docker

To host containers in development environments and provide additional developer tools, Docker

ships Docker Community Edition (CE) for Windows or for macOS. These products install the necessary

VM (the Docker host) to host the containers. Docker also makes available Docker Enterprise Edition

(EE), which is designed for enterprise development and is used by IT teams who build, ship, and run

large business-critical applications in production.

To run Windows Containers, there are two types of runtimes:

• Windows Server Containers provide application isolation through process and namespace

isolation technology. A Windows Server Container shares a kernel with the container host and

with all containers running on the host.

• Hyper-V Containers expand on the isolation provided by Windows Server Containers by running

each container in a highly optimized virtual machine. In this configuration, the kernel of the

container host isn’t shared with the Hyper-V Containers, providing better isolation.

The images for these containers are created the same way and function the same. The difference is in

how the container is created from the image running a Hyper-V Container requires an extra

parameter. For details, see Hyper-V Containers.

Comparing Docker containers with virtual machines

Figure 2-3 shows a comparison between VMs and Docker containers.

Virtual Machines

Docker Containers

Virtual machines include the application, the

required libraries or binaries, and a full guest

operating system. Full virtualization requires more

resources than containerization.

Containers include the application and all its

dependencies. However, they share the OS kernel with

other containers, running as isolated processes in user

space on the host operating system. (Except in Hyper-

V containers, where each container runs inside of a

special virtual machine per container.)

Figure 2-3. Comparison of traditional virtual machines to Docker containers

剩余339页未读，继续阅读

caoyongxu730

粉丝: 1
资源: 7

.NET微服务架构：面向容器化的Microsoft解决方案

NET-Microservices-Architecture-for-Containerized-NET-Applications.pdf

NET-Microservices-Architecture-for-Containerized-NET-Applications-中文版.rar

NET-Microservices-Architecture-for-Containerized-NET-Applications

Awesome-Microservices-NetCore：。一系列很棒的培训系列，文章，视频，书籍，课程，示例项目和.NET Core中的微服务工具

.NET Microservices:Architecture for Containerized .NET Applications

microservices-dotnetcore-docker-sf-k8s：展示一种使用.Net Core，Docker和Azure Service FabricKubernetes，基于域驱动设计（DDD）以及Comand和查询责任隔离（CQRS）等方法与基于微服务的体系结构一起工作的方法。模式

Spring Microservices_Build Scalable Microservices with Spring, Docker, and Mesos

spring.microservices.in.action

run-aspnet-grpc：在微服务中使用gRPC与.Net 5建立高性能的服务间通信。请参阅gRPC微服务和.NET课程的分步实施w折扣->

Micro-service framework in Go.zip

最新资源