One of the really great things about ORM’s that implement the Active Recordpattern like Eloquent is, they are really easy and really intuitive to use. With Active Record, you basically just have an object that you can manipulate and then save. Calling `save()` on the object updates the database, and all of the magic persistence happens behind the scenes. Having the business logic of the object and the persistence logic of the database tied together definitely makes working with an Active Record ORM easier to pick up. In this tutorial I want to explore exactly how Doctrine 2, an ORM that implements the Data Mapper pattern, is different to Eloquent.