As you’ve seen in the previous chapter, organizing the structure of a service is a complex matter: the number of parts, what duties they should have, the boundaries between them—it all has to be carefully considered. The focus of DDD was mainly on language and boundaries and cooperation between domain experts and tech experts, but it also offered some sort of direction on how to organize the code. In fact, we talked about layers, but we never explained what they are and let you have an instinctive idea of what they mean.

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Hexagonal Architecture

  • Delio D’Anna

摘要

As you’ve seen in the previous chapter, organizing the structure of a service is a complex matter: the number of parts, what duties they should have, the boundaries between them—it all has to be carefully considered. The focus of DDD was mainly on language and boundaries and cooperation between domain experts and tech experts, but it also offered some sort of direction on how to organize the code. In fact, we talked about layers, but we never explained what they are and let you have an instinctive idea of what they mean.