liveBook · Manning

Active record pattern

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

The active record pattern combines an object representing a domain record with the methods that persist and retrieve that record from a database.

The active record pattern combines a domain record with the methods that persist and retrieve it from a database. This coupling can accelerate early delivery, but may make code harder to understand, change, and scale as the domain grows. section 12.5

Gigs platform expansion

A gigs platform used Ruby on Rails to reach product-market fit quickly. As it expanded from the Netherlands into Germany, coupling domain and persistence logic made regional domain changes, third-party integrations, and team growth more difficult. section 12.5

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines the coupling and traces its maintenance and scaling consequences, but stops short of implementation detail.
Examples
Uses a Netherlands-to-Germany gigs-platform expansion to expose regional-model, integration, and team-scaling pressures.
What you can do after
Evaluate how coupling domain and persistence logic affects changeability, understandability, and scalability.
How it connects
Connects domain models with database models, persistence logic, convention-over-configuration, and domain evolution.

Also explained in

Compare how 3 books explain active record pattern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.