ManageRepository

What problem does it solve?

A repository is a critical boundary in the data layer; without clear guidelines, teams risk inconsistent interfaces, duplicated patterns, and brittle persistence strategies across features.

Core Features & Use Cases

• One repository per feature/module linked to a single AggregateRoot to ensure clean boundaries.
• No business logic in repositories; data persistence and retrieval are separated from domain rules.
• Use store() for both create and update operations, and find*() methods for queries; soft deletion is performed via delete() without hard removal.

Quick Start

Apply the guidelines by identifying the feature's AggregateRoot, enforcing a single repository, and using store for persistence and find* methods for queries.