Live data from Hacker News

.NET Micro ORM Review - FluentData

codecognition.org

1–10 of 16 posts

Re: .NET Micro ORM Review - FluentData

#5
post #2

What's the point of this when you have EF?

EF is a massive 'enterprise' codebase aimed predominately at SQL Server. If you don't need all the features ORMs like EF (or NH for that matter) offer (with all their associated config) then a micro-orm maybe better suited.

Dapper has been very useful at my current gig and more innovation in that space the better. Okay these micro-ORMs lack fundamentals like identity maps and caching but do you always need these features?

Inertia is dangerous.

Re: .NET Micro ORM Review - FluentData

#6
post #2

What's the point of this when you have EF?

Doesn't it suck?

No, Dapper does not suck. I too have been using Dapper at our company recently and its been an incredible boon to our db performance and code readability.

Plus, if its good enough for the Stack Exchange team, then its plenty good enough for me.

Re: .NET Micro ORM Review - FluentData

#8
post #6

Earlier quoted context omitted.

Doesn't it suck?

No, Dapper does not suck. I too have been using Dapper at our company recently and its been an incredible boon to our db performance and code readability. Plus, if its good enough for the Stack Exchange team, then its plenty good enough for me.

The "Doesn't it suck" comment was not directed at Dapper.

Re: .NET Micro ORM Review - FluentData

#10

Exhibit A: Yet another proof for having three obligatory pieces of software for every beginning programmer: an ORM, a blog engine and a CMS. On a more serious note, FluentData is a wheel reinvented, square. PetaPoco anyone?

There are several micros (I'm sure you know) but I love the micro, micro approach of Peta. I'll admit that up until recently, I've always setup my own classes with data myself. Looking back on projects, it actually hasn't been that bad. These are medium sized applications and, yes, setting up properties is super annoying and can take a while but, in retrospect, it hasn't cost me that much really, I don't see how I could save more than a few hours with an ORM and I have 100% control over my database interactions, code separation, complete knowledge about exactly what it is doing, and a fast application.

I like Peta because it's the smallest most minimal ORM I've found. I can grasp most of what it's doing after little work with it and it's fast enough for me though I'm definitely not pushing it too hard.

Post reply on HN