Feat/ddd

[CarlosSimon02]

DDD Implementation

Overview
Implement Domain‑Driven Design (DDD) across Finora core domains to centralize business logic, improve testability, and increase maintainability.

Why

• Business logic was scattered and duplicated.
• Adding features risked breaking unrelated areas.

What changed (high level)

• Domain layer created: value objects and entities for Transaction, Pot, Budget, Income, and shared types.
• Value objects: 19 self‑validating VOs (Money, IDs, Names, MaximumSpending, etc.).
• Entities: 5 aggregates with business logic (Transaction, TransactionCategory, Pot, Budget, Income).
• Use cases refactored: 37 use cases now thin orchestrators using domain objects.
• Documentation: 5 docs added (DDD guides, before/after, quick reference).

Benefits / Impact

• Centralized business logic and validation
• Safer, unit‑testable domain code (DB not required for domain tests)
• Reduced validation duplication (≈93% reduction)
• API contracts, DB schema, and repository interfaces unchanged

Backward compatibility

• No breaking changes: public APIs and DB schema unchanged; repo interfaces preserved.

Notes for reviewers

• Focus on src/core/entities/ and src/core/valueObjects/ (validation and invariants).
• Review refactored use cases in src/core/useCases/ for thin orchestration.
• See docs/ for patterns, examples, and migration notes.

Next steps / opportunities

• Use domain events for notifications, analytics, payment integrations, and outbox patterns.

---

Summary: Centralized domain logic with DDD — safer, cleaner, and easier to extend. Ready for review.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
finora	Ready	Preview	Comment	Nov 10, 2025 1:59am