|
|
|
|
|
by acesubido
2918 days ago
|
|
ORM's are nice for majority of writes and simple reads based off of an object (a model). It starts to hinder once there's a requirement for complex reports. I find, that's where the distatse of ORMs in an organization starts. The other way to deal with majority of these complex reports is to create a separate OLAP table (model) to write/update too, and pull aggregates from there. But that's treading on a thin line of over-engineering. ORM's are supposed to be used for Objects. If a report isn't a well-defined object/model, then it's going to fight against an ORM. |
|