title: .NET Repository Pattern and Http Requests
body: <p>I am trying to 100% understand the patterns of architecture in the .NET world. The Repository main code of the Repository Pattern as far as i know is usually created in the infrastructure layer, for data access, not only to databases but other cases as well. To this day, i've only seen it being used for access to the database, but i would like to see if possible, multiple other examples for when using a Repository class.</p>
  <p>Right now for example, i'm building an application that does Http Requests to multiple other APIs. I have a Domain/Core layer, and an Infrastructure layer. What would be the best practice in this case for the Http Requests class? Should there be Repositories for the HttpRequests communication classes? Or is there another pattern to follow in this case?</p>
  <p>If possible and someone could give some more detailed material on this subject i would be thankful. I have searched a lot and all i can find is always the same database only related repository access.</p>