Which Micro ORM to use?

Question

Trying to decide between Dapper , Massive and PetaPoco . I like the simplicity of Dapper, the flexibility of supporting Massive and POCO at PetaPoco, but I'm currently delaying which one to choose for my next project.

I understand that to a large extent this is a matter of personal taste, but I think it will be useful to hear some opinions on this issue, especially from people who have tried more than one of them, errors, libraries (which is the correct term: library, file , structure?)

Answer 1

Try to decide which of the features you mentioned - simplicity, flexibility, POCO support - will be most useful to you and your project (s) in a year. . Most likely to facilitate your work?

Then you will have your answer. And if you still can’t choose, choose Dapper (just a random choice I made :-) As the Cheshire Cat says, if you really don’t know where you want to go, it doesn’t matter which way you choose.

Answer 2

PetaPoco documentation seems more mature than others. This seems to be the safest route.

Answer 3

i havent triend any of them. by default, I always base my decision on the number of lines of the received client code and the type of security. Of course, there are a number of other indicators that you should consider, but if your project is not limited by any special (exotic) requirements, then these two are usually applicable. By the way. I know about the disputes that my answer may have;)