V3 Core Implementation

Start with base classes for Entity, ValueObject, and AggregateRoot that handle identity equality and domain events. Then organize code into bounded contexts with entities, value objects, services, and repositories per domain, keeping domain logic free of infrastructure dependencies.

Separate code into domain, application, and infrastructure layers. The domain layer holds entities and business rules, the application layer contains use cases and command handlers, and infrastructure provides repository implementations, event buses, and loggers wired through a DI container.

Inversify works with TypeScript decorators when you enable experimentalDecorators and emitDecoratorMetadata in tsconfig. Bind interfaces to implementations in a container using symbols as service identifiers, then resolve dependencies through constructor injection.

Test entities as plain unit tests without databases by asserting state changes and emitted domain events after method calls. Use in-memory SQLite databases for repository integration tests to verify mapping between rows and reconstituted aggregates.

Raise domain events inside aggregate methods when significant state changes occur, such as task assignment or completion. Collect uncommitted events on the aggregate, publish them after persistence succeeds in the use case, then mark them committed.