What is the best practice abstraction patterns for the data layer?

I wanted to know what are some patterns for abstracting the data layer so that you can plug in any framework like entity framework or dapper or straight up ado.net wrappers or any database like sql server or postgresql. I know that there are patterns like repository pattern and unit of work pattern and service pattern, but can anyone give me like a high level description of how it all fits together and what the purpose of each layer of abstraction is supposed to do?

submitted by /u/NetFutility
[link] [comments]

Leave a Reply