Skip to content

Help with architecture Domein Driver Desing #164389

Discussion options

You must be logged in to vote

Hi @Andrii-Bilonohov ,

I see you’re trying to understand how to structure and comment on each layer in a Domain-Driven Design (DDD) inspired architecture. Based on your folder names and typical DDD patterns, here’s a detailed breakdown of what each layer is responsible for:

1. Application Layer (e.g., nasas.application):

      - Acts as a bridge between the UI/presentation and the domain.
      - Contains business workflows, use case orchestration, service interfaces, and DTOs.
      - It shouldn’t contain core business logic but can coordinate domain objects.
      - Example: Command/query handlers, application services.

2. Domain Layer (e.g., nasas.domain):

      - The heart of your bu…

Replies: 2 comments 2 replies

This comment was marked as off-topic.

@Leorev01

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Ask and answer questions about GitHub features and usage Programming Help Discussions around programming languages, open source and software development
2 participants