Content Provider是Repository Pattern的实现吗？(Is Content Provider an implementation of Repository Pattern?)

 存储库模式由Hieatt和Rob Mee定义为设计模式，它使用类似集合的接口访问域对象，在域和数据映射层之间进行调解 。 
 
  
 
 基本上，它将一个或多个I / O设备（云，磁盘，数据库等）抽象为一个通用的类似集合的接口，您可以在其中读取，写入，查找和删除数据 。 
 
 在Fernando Cejas的Android Clean Architecture上 ，应用程序需要的所有数据都来自该层，通过使用存储库模式的存储库实现（接口位于域层中），其策略通过工厂根据不同的数据源选择不同的数据源一定条件下。 
 
  
 
 然而，正如Coursera课程的 Douglas Schmidt教授指出的那样，内容提供者管理和调解对一个或多个应用程序的数据中央存储库的访问 
 
  
 
 在编程Android手册中 ，内容提供者被用作RESTful Web服务的Facade 。 这种方法最初由Virgil Dobjanschi在Google I / O 2010期间提出。 
 
 因此，为了不使用内容提供者访问本地SQLite数据库 ，为什么不使用它作为存储库模式本身呢？ 
 
  

Repository Pattern is defined by Hieatt and Rob Mee as design pattern that mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects.
 
 
Basically it abstracts one or more I/O devices (cloud, disk, data base, etc) into a common collection-like interface where you can read, write, seek and delete data.
 
On Fernando Cejas's Android Clean Architecture, all data needed for the application comes from this layer through a repository implementation (the interface is in the domain layer) that uses a Repository Pattern with a strategy that, through a factory, picks different data sources depending on certain conditions.
 
 
However, as pointed out by professor Douglas Schmidt at Coursera course, content provider manages and mediates access to a central repository of data to one or more applications
 
 
In the book Programming Android, content providers are used as a Facade for a RESTful Web Service. This approach was initially presented by  Virgil Dobjanschi during Google I/O 2010.
 
Thus, instead of using content providers to access the local SQLite database, why not using it as the repository pattern itself?
 

原文：https://stackoverflow.com/questions/43258773