This limitation is very annoying, you can still load parent/child object, but you have to construct your SQL query special way or do multiple queries, also when saving parent, you should not forget about children. Relationships: there is no one-to-one, many-to-many relationship supported, which means, when you load an object from the database, all related objects will not be automatically loaded or saved, if you want to load related objects, you have to construct your query special way.Frankly speaking, it’s not a huge limitation and it’s very easy to solve it just applying. Caching: Second Level Cache is not supported, so if you need it, you have to implement some kind of database caching yourself.Below you can see the most important limitations of Micro Orm:

What are the limitations of Micro ORM?įrom my experience, you can live with some limitations for micro ORM, but some can stop you from using it in favour of full-featured ORM tools. It means that MicroORM suppose to do the same job of mapping table to object, but it sacrifices a number of features to have a better performance. You probably already know what is the Micro ORM, but if not: Micro ORM is a lightweight ORM, usually limited in features, but performing faster than full-featured ORM. When talking about full-featured ORM, it’s usually Entity Framework or NHibernate. Peta Poco is similar to Dapper but makes you write less SQL because of using attributes on your model. The most popular is Dapper, from StackOverflow, it also the fasters of all existing. When talking about micro ORM it usually does not matter which one to use, the differences are usually very small. I have used Micro ORM for one of my projects recently and want to share my experience with such micro ORM as Dapper or Peta Poco, as well as compare them with such ORM tools as EntityFramework or NHibernate.

Dapper orm