Active record pattern: Difference between revisions

Revision as of 13:07, 15 November 2019

Revision as of 18:01, 29 November 2019

Line 36:

=== Single responsibility principle and separation of concerns ===

Another critique of the active record pattern is that, also due to the strong coupling of database interaction and application logic, an active record object does not follow the

[[single responsibility principle]] and [[separation of concerns]] as opposed to [[multitier architecture]] which properly addresses these practices.{{citation needed |date=November 2019}} Because of this, the active record pattern is best and most often employed in simple applications that are all forms-over-data with [[Create, read, update and delete|CRUD]] functionality, or only as one part of an architecture.{{citation needed |date=November 2019}} Typically that part is data access and why several ORMs implement the active record pattern.

=== Distributed systems ===