domain-modeling

Structure BIM domain logic using hexagonal architecture by organizing code under packages/domain/src/<context>/ with entities, value objects, and domain services. This separates domain logic from infrastructure, defining ports and adapters to ensure testable, platform-agnostic code.

Domain modeling defines entities, branded types, value objects, and domain errors within a hexagonal architecture. You need branded types and domain errors to enforce consistent domain boundaries, robust type safety, and standardized error handling across application contexts.

Create a new domain entity by defining its ID type, entity class, domain service, and repository port within packages/domain. Follow the hexagonal pattern to specify exports and adapters, ensuring the domain logic remains isolated and testable.

Domain-driven design works for managing multiple bounded contexts by defining separate boundaries such as account, auth, payment, swap, user, and shared. This promotes consistent domain modeling, reuse, and standardized state machines across distinct application contexts.

The best way to separate domain logic from infrastructure is applying hexagonal architecture with domain-branded types, ports, and adapters. This pattern isolates domain services and entities, yielding platform-agnostic code that supports robust and independent testing.

You need domain services and repository ports in domain-driven design to abstract infrastructure dependencies and define clear boundaries. Ports specify required operations while adapters implement them, ensuring domain entities and value objects remain testable and platform-agnostic.