Last post Apr 17, 2015 09:20 AM by DeadTroll
Apr 17, 2015 08:25 AM|sudip_inn|LINK
for a long time our organization is using MSDAAB (Microsoft data access application block) and it is normal DAL not ORM. we are happy to use it. all controls in our hand for data fetching optimization. now we are thing to move to EF but do not know is it
at all good for a db which has huge data.
please guide me about the performance of EF with db first approach for a database which may have huge data. when should one think about EF to use because many guys said EF performance is not good rather NHibernate as ORM is good in terms of performance.......what
is others opinion ?
Apr 17, 2015 09:20 AM|DeadTroll|LINK
Opinions vary. I'm currently working EF6 Code First with Migrations and I like it. I had a few bumps in the road due to automatic migrations which caused me to move to coded migrations. Learning curve isnt very steep. DB First is nice with any ORM and works
well after initial development of the data structure. If your database is still in infancy I would suggest not using DB First otherwise its a solid implementation. I can't speak to NHibernate much though. I did do some comparison a few months back when I started
using EF6 and found that current development of NHibernate is lacking while EF is advancing at a much faster pace. With EF6 I believe Nhibernate is now lacking some key features.
Here's an article that delves deeper into the topic.
Here's another article