> No, you shall not do a User.where directly, you have to do a > UsersRepository.find_all_with_email(...).

Even that seems weird to me. If want to load objects, I want to load them from a particular repository, not a class of repositories (which the upper-casing of `UsersRepository` suggests).

As soon as your app needs to talk to more than one data source, this business where data is tightly coupled to a particular datasource by the framework makes a big mess.

But that's why I don't use Rails in the first place.

Yeah, show me the EntitlementRepository and all its dependencies. There’s Users, UsersProfile, Address, BillingProfile, Subscription, SubscriptionSet, and Mailer. You might even have it down the the rbac level.

Glad it’s satire.

You mean the `def user_repository_provider` on the controller I believe?