8000 Promote the Anemic Domain Model as best practices? · Issue #7460 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content
Promote the Anemic Domain Model as best practices? #7460
Closed
@Federkun

Description

@Federkun

I was looking at the Symfony Demo application, and then I asked myself: it's really okay to promote anemic domain model as "best practice"?
I was reading the Doctrine Mapping Information section in particular:

Doctrine entities are plain PHP objects that you store in some "database".

But real entity has behaviors. From what I read there, I understand that "Doctrine entities are basically DTO".

I acknowledge that's the simpler way to explain how to build your "model", and for a demo app it's okay, but it isn't really a good practice, isn't it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0