Repository vs. DAO (again)
问题 In general this back-story does not matter but just to explain the code below: The server handles users and user groups. User groups are able to "discover" places - at this point in time these places are coming exclusively from the Google Places API. Current Implementation Currently, I have a lot of JpaRepository objects, which I call Repository , in my Service Layer. I am stressing " Repository " because in my proposed solution below, they'd be downgraded to DAOs. However, what I do not like