Enhancement: Repository pattern interfaces

[fkromer]

Summary

It's common practice to provide generic interfaces for implementing the repository pattern. It makes sense to provide several interfaces for specific types of application designs. CrudRepository is suitable for abstracting persistence of CRUD models. More generic repository interfaces are required for domain driven designs (DDD) involving aggregates, entities (value objects persisted as part of entities). Data abstraction objects (DAOs) can be seen as simple variants of a repository pattern or as an own pattern category (DAOs vs Repository).

Examples:

• Spring Data Repository / usage reference

Basic Example

No response

Drawbacks and Impact

Impacts:

• enables domain driven designs of different complexities

Unresolved questions

• Should DAO patterns be considered separately from repository patterns?

---

Note

While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.

Check out all issues funded or available for funding on our Polar.sh dashboard

• If you would like to see an issue prioritized, make a pledge towards it!
• We receive the pledge once the issue is completed & verified
• This, along with engagement in the community, helps us know which features are a priority to our users.

[provinzkraut]

This already exists :)

https://docs.litestar.dev/latest/usage/databases/sqlalchemy/models_and_repository

In fact, there's a whole repository dedicated to this (and more): https://github.com/litestar-org/advanced-alchemy