Skip to content

Consider alternatives to Doctrine for ORM #56

@skluck

Description

@skluck

Doctrine is great, but complex.

There are some things it doesn't do super well:

  • Migrations / Schema
  • Entities from multiple libraries (E.g. modular db schema)
  • Fine-tuning performance (e.g.control over nested/chained queries / lazy loading)
  • Class/Namespace structure of entities

I like what I've seen out of Atlas ORM:
https://github.com/atlasphp/Atlas.Orm (doc example: http://atlasphp.io/mapper/domain.html)

Its goal is mapping data to and from the DB, but not your domain models. That is up to the application. Leaving that control in the hands of the app may gives us more control to tune and tweak things for our use cases, and be more concious of the data we fetch from the db.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions