Do You Need a Repository Pattern?

JD Regan: Most of our applications now are in a microservices context where each microservice should be very easy to understand, does not manipulate a lot of entities. So I would maybe use something like a repository pattern, but in a much more specific and strongly typed way because I know from where to when I'm switching from and to. He says that people tell you why you should not use it unless proven otherwise, but really it should come to mind whenever it's needed. "I think solid principles were created more for extending your code," he adds.