When comparing Propel 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 Propel is ranked 5th. 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
It requires some learning curve, but at the end it's a powerful and versatile ORM. We've been using it for a very big database in a realtime multi-frontend app with zero issues.
Pro Support for a large number of databases
Since it uses PDO, it supports all PDO enabled databases, with MySQL, SQLite, PostgreSQL, MSSQL, Oracle included.
Pro Simple to learn
Propel uses Active Record, which is a rather simple to understand implementation of an ORM. It's also the most widely adopted implementation. In simple words: an object represents a row, you can create or edit an object to create or edit the corresponding row.
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 Backward compatibiliy breaks
Since it's based on PHP 5.4+, using an older version of PHP may cause issues.
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.
Alternative Products
