Support the ongoing development of Laravel.io →
Architecture
Last updated 2 years ago.
0

I don't quite agree with your understanding of "repository". Imho it should NOT have application logic and also it is not in between something => it just adds another layer of abstraction to the data source.

Everything else is like I do it: I have a Business/Domain Object which uses Services to check/modify Repositories.

Last updated 2 years ago.
0

Langdi said:

I don't quite agree with your understanding of "repository". Imho it should NOT have application logic and also it is not in between something => it just adds another layer of abstraction to the data source.

Everything else is like I do it: I have a Business/Domain Object which uses Services to check/modify Repositories.

I meant CRUD on data source only, not validation or something.

Last updated 2 years ago.
0

Bump` Waiting for opinions.

Last updated 2 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.