How to create abstract layers between various ORMs (entity framework and Dapper)?

Question

I want to create abstract layer between entity framework and Dapper.In runtime i can choose either entity framework or Dapper or i will both of them also. I know that i can use interface

public IORM{
    Save();
    Delete();
    //other ORM functions
}

public EntityFramework : IORM{
    public Save(){
    SaveChanges();
    }
    public Delete(){
    Remove();
    }
}


public Dapper: IORM{
    public Save(){
    //save code goes here
    }
    public Delete(){
    //delete code goes here
    }

But this is basic operations and not sure how to configure in .net core 2.0 CofigureServices() Method.

Is abstractions between different ORMs advisable? If yes how to implement abstract layer between Entity framework and Dapper in .net core 2.0?

Unless the application requirements need to use both sql and nosql databases ( some kind of hybrid use case ) I would not advise abstracting the ORM's . So evaluate the use case from the point of view of current and future requirements , if your application and live it's full live with one type of Database then no need to abstract. — Soumen Mukherjee
– Soumen Mukherjee, Commented Oct 4, 2017 at 7:53
I would say that creating an abstraction layer between different ORMs is not particularly useful. It would take quite a bit of efforts and the return on investment seems unlikely. After all, why would you make the switch? — GlennSills
– GlennSills, Commented Oct 7, 2017 at 21:39

mbnx · Accepted Answer · 2017-10-04 07:54:39Z

It is always advisable to keep concerns separated. But it is an illusion that a full blown ORM can be hidden behind one interface definition. The runtime behavior of the ORM can have quite some consequences for the whole application and it will need alot of work to be able to just "swap" the ORM. There are not many good reasons to maintain that ability. What is your motivation behind that?

Of course, it is a good idea to abstract the concrete ORM work. Concrete examples really depend on your overall architecture, but to mention some points:

Keep persistence stuff (Attributes, dependencies) out of the model and controllers.
Apply the repository pattern and inject repository interface parameters into your application services. This way, you can hide concrete query / write operations of the ORM.
Apply the unit of work pattern and handle the Unit of Work transparently per request using the web framework infrastructure. This way, you can hide concrete transaction handling operations of the ORM.

Collectives™ on Stack Overflow

How to create abstract layers between various ORMs (entity framework and Dapper)?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related