I think you might be assuming that there's a single dev team using the model/domain to do things with the data. Often, at least in big enterprise dev, there wil

I think you might be assuming that there's a single dev team using the model/domain to do things with the data. Often, at least in big enterprise dev, there will be other teams doing things: Batch processing teams with their own apps, Data Service teams doing their own things. And they will all doing this likely outside the standard dev-centric data access. And then, what sometimes happens is that even a second team gets asked to innovate on the same data store, which can potentially bring in yet another code-to-db layer. (Granted this is ideally not a great place to be at, but due to time, cost. etc. it does happen). I generally agree with you, though. In my ideal world, people working on the batch, offline processing, etc. would be integrating through a centralized API...