View Revisions: Issue #15395

Summary 15395: Split models into services and DAO (data access objects)
Revision 2019-10-10 17:17 by ollehar
Description "Fat models" pattern leads to less testability and too big classes. We should split all models into two categories:

```
models/
    services/
        ParticipantService.php
        ...
    dao/
        Participant.php
        ...
```

or similar. DAO extends active record, services do not and can be stateless or statefull.

Much functionality in controllers should be moved into services too.
Revision 2019-10-10 17:03 by ollehar
Description "Fat models" pattern leads to less testability and too big classes. We should split all models into two categories:

```
models/
    services/
        ParticipantService.php
        ...
    dao/
        Participant.php
        ...
```

or similar. DAO extends active record, services do not and can be stateless or statefull.
Revision 2019-10-10 17:02 by ollehar
Description "Fat models" pattern leads to less testability and too big classes. We should split all models into two categories:

```
models/
    services/
        ParticipantService.php
    dao/
        Participant.php
```

or similar. DAO extends active record, services do not and can be stateless or statefull.
Revision 2019-10-10 17:02 by ollehar
Description "Fat models" pattern leads to less testability and too big classes. We should split all models into two categories:

models/
    services/
        ParticipantService.php
    dao/
        Participant.php

or similar. DAO extends active record, services do not and can be stateless or statefull.
Revision 2019-10-10 17:01 by ollehar
Description "Fat models" pattern leads to less testability and too big classes. We should split them all models in two categories:

services/
dao/

or similar. DAO extends active record, services do not and can be stateless or statefull.