We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When is a Use Case layer needed? https://softwareengineering.stackexchange.com/questions/166462/when-is-a-use-case-layer-needed
DDD - Are 'use cases' and 'application services' different names for the same thing? https://softwareengineering.stackexchange.com/questions/366188/ddd-are-use-cases-and-application-services-different-names-for-the-same-th
In my thoughts, use case 好處是易懂,且不會跟 domain service 搞混,缺點是要建立一個 use case 建立一個檔案。
Application service 好處是不必被 domain aggregate object 給影響 (不會受限於要用 booking, room, customer 做分類)
The text was updated successfully, but these errors were encountered:
UseCase or ApplicationService?
Sorry, something went wrong.
No branches or pull requests
When is a Use Case layer needed?
https://softwareengineering.stackexchange.com/questions/166462/when-is-a-use-case-layer-needed
DDD - Are 'use cases' and 'application services' different names for the same thing?
https://softwareengineering.stackexchange.com/questions/366188/ddd-are-use-cases-and-application-services-different-names-for-the-same-th
In my thoughts, use case 好處是易懂,且不會跟 domain service 搞混,缺點是要建立一個 use case 建立一個檔案。
Application service 好處是不必被 domain aggregate object 給影響 (不會受限於要用 booking, room, customer 做分類)
The text was updated successfully, but these errors were encountered: