When comparing Lean Mapper vs Eloquent ORM, the Slant community recommends Eloquent ORM for most people. In the question“What are the best PHP ORMs?” Eloquent ORM is ranked 3rd while Lean Mapper is ranked 15th. The most important reason people chose Eloquent ORM is:
Sometimes your issue can be hard to find, but certainty it was already answered before.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Powerful and versatile ORM
Pro Open source
Pro Good & constant support
Pro Stable
As the code hasn't been drastically changed in the past few years, there is no further learning required once its been learned once.
Pro Smart relationship loading
Pro Support for a large number of databases
Since it uses Dibi, it supports all Dibi enabled databases, with MySQL, SQLite, PostgreSQL and more included.
Pro Framework Agnostic
Pro Friendly community
Pro Large community
Sometimes your issue can be hard to find, but certainty it was already answered before.
Pro Good documentation
While hard to find, the Laravel's Docs and API documentation are very good.
Pro Fast learning curve
Laracast and other public resources can set up your learning curve as fast as possible.
Cons
Con Too much magic methods
The debug hell.
Con Low performance
Eloquent tries to do too much magic, it gets slower than some concurrents.
Con No own datamapping
You gotta install plugins to be able to map your eloquent models; or you can use mutators, that results in very ugly model classes.