Is it better to have a repository per model (this could be a class that represents a table from the database) or should just have one big repository for all data access methods?I have done the second approach and have found it to get way out of hand, but maybe somewhere in between is a solution as well.
How granular should we get with repositories?
design patterns;architecture;repository
Why are repositories any different from other classes?A class should have a single responsibility - a single reason to change. If you have a bundle of related data sources that are (necessarily) tightly coupled, then it can make sense to have a single repo to deal with all of them. If you have some unrelated tables, then it's probably better to have a single repository per table. 