entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://martinfowler.com/tags/domain%2520driven%2520design.html|1|https://martinfowler.com/articles/microservices.html|blocks|key|2eslq|text|微服务和DDD之间没有关系...是的，你肯定可以在没有另一个的情况下做到这一点。有界上下文是域级别和微服务它是一个实现/基础设施/体系结构，如果你想的话它们可以是相关的……|unstyled|depth|inlineStyleRanges|entityRanges|6fo1o|Domain+Driven+Design是Eric+Evans在2003年引入的一组战术和战略设计原则……处理软件中的复杂性|offset|length|f98qo|Microservices是一种架构，用于将应用程序设计为可独立部署的服务套件|2e6fj|CQRS和Event+Sourcing是实现领域驱动设计(可以被视为DDD中的构建块)的一种方式，但它们可以像其他构建块一样在DDD之外使用。|93fe6^0|0|0|K|0|0|0|D|1|0|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|T|I|@]|J|@]|6|$]]|$C|K|E|L|2|G|H|U|I|@]|J|@$M|V|N|W|C|X]]|6|$]]|$C|O|E|P|2|G|H|Y|I|@]|J|@$M|Z|N|10|C|11]]|6|$]]|$C|Q|E|R|2|G|H|12|I|@]|J|@]|6|$]]|$C|S|E|-4|2|G|H|13|I|@]|J|@]|6|$]]]]

No relationship between Microservices and DDD... And yes you can definitely do one without the other.
Bounded context is domain level and microservice it's an implementation/infrastructure/architecture whatsoever, they can be related if you want to...

<a href="https://martinfowler.com/tags/domain%20driven%20design.html" rel="nofollow noreferrer">Domain Driven Design</a> is a set of tactical and strategical design principles introduced by Eric Evans in 2003... to tackle complexity in software 

<a href="https://martinfowler.com/articles/microservices.html" rel="nofollow noreferrer">Microservices</a> is an architecture for designing an app as suites of independently deployable services

CQRS and Event Sourcing are a way to implement a Domain Driven Design (could be seen as building block in DDD), but they could be used outside DDD like the other building blocks.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook|blocks|key|e4d0o|text|尽管我同意@rad的回答，但微软最近出版了一本关于微服务和asp.net核心的电子书，其中他们成功地将微服务和asp.net结合在一起。|unstyled|depth|inlineStyleRanges|entityRanges|7n940|请参阅https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook|offset|length|533b7^0|0|3|29|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|N|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|O|G|@]|H|@$K|P|L|Q|A|R]]|6|$]]|$A|M|C|-4|2|E|F|S|G|@]|H|@]|6|$]]]]

Eventhough I agree with the answer from @rad Microsoft recently published an ebook about microservices and asp.net core in which they combine microservices and DDD successfully.

See <a href="https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook" rel="nofollow noreferrer">https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook</a>

entityMap|blocks|key|6vlbp|text|我认为微服务和DDD有不同的起源，但我们两者都需要。了解如何：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|48fe|DDD说明了如何围绕业务领域分解和设计您的软件|e9buj|微服务说，在规模较小的独立服务中中断并设计您的业务域|dpflc|现在，如果你仔细观察，可以讨论break和将你的软件设计成更小的部分，服务方面的微服务(用于扩展)和DDD方面的有界上下文(用于设计)。|agk2g|此外，微服务需要一致性，而DDD战术策略有助于设计最终的一致性系统|8uth0|为了解决一个大的业务问题，我们需要DDD和微服务，并且需要在它们之间找到一个良好的对应关系。|ais8c|在我看来，任何微服务都不能跨越一个有界上下文，而且一个有界上下文可以有多个微服务.And。微服务之间的依赖主要由有界上下文之间的映射来控制|7ttko^0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|S|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|T|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|U|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|V|9|@]|A|@]|B|$]]|$2|O|4|-4|6|7|8|W|9|@]|A|@]|B|$]]]]

I think microservices and DDD have different origin but we need both. See how: 

DDD says how to break and design your software around the business domain

Microservices says break and design your business domain in smaller sort of independent services to scale

Now if you look closely both talk about break and design your software into smaller pieces, microservices in term of services(for scaling) and DDD in terms of Bounded Context(for design). 

Also microservices need consistency which can be eventual only and DDD tactical strategy helps in designing eventual consistent system 

To solve a big business problem we need both DDD and Microservices, and need to find a good cor-relation between them.

From my perspective no microservice can span a bounded context , also one bounded context may have multiple micorservice .And the dependecny between microservices is majorly governed by mapping between bounded context

entityMap|blocks|key|6pu5e|text|它们之间没有关系。您可以在没有ddd、cqrs或es的情况下执行微服务。它们服务于不同的目的，虽然微服务架构关注高可用性、可扩展性和其他更关注实际业务需求的问题，但DDD关注的是编码风格。CQRS与微服务属于相同的关注点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3cue4^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|D|9|@]|A|@]|B|$]]|$2|C|4|-4|6|7|8|E|9|@]|A|@]|B|$]]]]

There is no relation between them. You can do microservices without ddd, cqrs or es.
They server different purposes and while a microservice architecture focuses around high availability, scalability and other concerns more focused around the actual business needs, DDD focuses on coding style. CQRS falls under the same umbrella of concerns as microservices do.

For the last couple of weeks I've been starting and trying to understand DDD CQRS, ES and Microservices. 
I think I've understood them individually but not as a single unit so this is why I have some misunderstandings that I hope to clarify.

So first what is the relation between Microservices and DDD, can you do one without the other?
And secondly, does Bounded Contexts translate in the end into a microservice ?

Relation of Microservices and DDD CQRS and ES

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 在过去的几周里，我一直在尝试理解DDD CQRS、ES和Microservices。我想我已经单独地理解了它们，但不是作为一个整体，所以这就是为什么我有一些误解，我希望澄清。 那么首先，微服务和DDD之间的关系是什么，你能做到一个没有另一个吗？其次，有界上下文最终是否会转换为微服务？ 

问微服务与DDD CQRS和ES的关系
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问微服务与DDD CQRS和ES的关系EN