问题描述
除了大师之外，我还没有找到关于该主题的任何具体内容
I haven't found anything concrete on the topic from the gurus, except
来自弗农·沃恩(Vernon Vaughn).
from Vernon Vaughn.
我担心的是，在DDD文献中，大多数ORM/查询都用作存储库的示例.我的项目在域逻辑上非常稀缺，因为它主要是几个API的包装，并结合了这些Context的结果.该项目的职责范围很广，可以适合整个企业的许多领域/背景.从一开始就唯一需要遵循的架构规则是洋葱架构，至少DDD技术建模概念对我来说似乎很合适.我必须说，在这个正在进行的特定项目中很难推断出领域.
What my concern is that mostly ORMs/queries are used as examples of Repositories in the DDD literature. My project is very scarce in domain logic cause it's mainly a wrapper on a couple of APIs and combines the outcome of those Contexts. The responsibilities of the project are broad and could fit many areas/contexts of the business as a whole. The only architectural rule forced from the beginning is the onion architecture and at least the DDD technical modeling concepts seem fitting for me. I must say it's hard to reason about the domain in this particular ongoing project.
推荐答案
也许吗?
存储库是一种模式，它是由关注点分离的概念所驱动的-在处理域逻辑时，您不必大惊小怪的持久化细节.
Repository is a pattern, motivated by the notion of separation of concerns -- you shouldn't have to fuss with the details of persistence when you are working on the domain logic.
这篇关于外部服务(API)是否适合存储库的DDD定义?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！