Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

66%
+2 −0
Q&A Hexagonal Architecture + Domain Driven Design. How to perform a correct implementation?

Adapters are implemented in different layers based on their function. Input adapters (like REST controllers) are at the application's edge to handle incoming requests, while output adapters (like d...

posted 7d ago by harmony‭

Answer
#1: Initial revision by user avatar harmony‭ · 2024-10-11T14:49:11Z (7 days ago)
Adapters are implemented in different layers based on their function. Input adapters (like REST controllers) are at the application's edge to handle incoming requests, while output adapters (like databases) are in the infrastructure layer, interacting with external systems.

Repositories and domain services are interfaces in the application layer, implemented in the infrastructure. Entities should handle the core logic, while repositories manage persistence.

For UseCases, it's often clearer to have separate interfaces for each, but you can combine them if they are related. Naming conventions vary, but consistency and clear, descriptive names are key.

Your structure looks well-organized. Stick to clear separation of concerns, and you'll be on the right track.