m09-domain

To model domain entities and value objects in Rust, you differentiate them by identity versus invariants, mapping entities to owned structs and value objects to immutable types. This skill provides checklists to select correct primitives ensuring clear ownership.

Defining aggregate boundaries in Rust applications requires grouping entities and value objects under an aggregate root to enforce transactional invariants. This skill provides templates to align architecture decisions and maintain traceability from domain rules to implementation.

Implementing the repository pattern in Rust involves defining traits for aggregate persistence to abstract data access. This skill guides selecting repositories and mapping them to Rust traits, ensuring domain models remain decoupled from infrastructure.

You choose an entity versus a value object in domain-driven design by checking for identity: entities have lifecycle identity while value objects are defined solely by attributes. This skill offers a quick checklist to determine identity, invariants, and ownership.

Yes, applying DDD patterns to existing Rust codebases with unclear ownership involves analyzing domain concepts to establish boundaries and invariants. This skill provides safety-focused guidance and ownership rules to refactor and align architecture decisions.