I've seen implementations of ORM's where the complicated joins of relational operations are embedded in the ORM definition. It's done for performance, without c

I've seen implementations of ORM's where the complicated joins of relational operations are embedded in the ORM definition. It's done for performance, without considering the impact on future business process review. This inherently hides that logic from external review. One of the things we need to enable as architects is to make sure the systems we build are adaptable. Any "framework" that begins to hide logic through efficiencies is bad architecture.