问HN：在什么情况下你开始考虑将采用领域驱动设计（DDD）构建的服务“分离”？
嗨，HN。
最近，我一直在 obsessing 关于 DDD 中的解耦时机。
无论我怎么思考，我觉得在实际经历之前是找不到答案的。所以我在寻找其他的观点。
如果你是维护使用 DDD 设计的应用程序的人，当某个领域的流量开始增加时，你是如何决定何时通过控制平面/数据平面进行分离的？
你是从一开始就将其视为架构问题，还是通常在系统增长后才会出现这种需求？
我很想知道这里的人们是如何在实际中做出这个决定的。
查看原文
Hi, HN.<p>Recently, I've been obsessing about decoupling timing in DDD.<p>No matter how much I think about it, I feel like I won't find the answer till I actually go through it. So I'm looking for other perspectives.<p>If you are someone who maintains application designed with DDD, and traffic of one domain starts getting higher, when do you decide it's time to separate by control plane / data plane?<p>Do you treat this as an architectural concern from the beginning, or does it usually emerge later as the system grows?<p>I'm curious how people here make that call in real.