Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
wild-workouts-go-ddd-example
Go DDD example application. Complete project to show how to apply DDD, Clean Architecture, and CQRS by practical refactoring.
I have actually never quite understood the distinction between a particular domain’s service and it’s use case. You mentioned that it seems redundant now but will prove useful later. Admittedly j have just started how to code, but consider myself intermediate/advanced beginner. I started on a CMS backend for restaurants based on Clean Architecture and still haven’t come across a reason to decouple the two. Can you provide clarification via an example?
or you can also do like this
Here's an example of a domain model using this approach.