Redis handles two fundamentally different jobs in Magento 2: write-heavy session storage and read-heavy caching, often on the same server without any clean separation. This article shows how to calculate the memory needs for Redis sessions, configure env.php and redis.conf for separate instances, and use monitoring to catch it early when Redis sizing hits its limits.

MODEL

DB

Deep Dive · Magento 2 Design Patterns

Active Record Pattern:
Magento Models and Their Database Connection

How AbstractModel and ResourceModel work together, why Magento adapts the classic Active Record Pattern, and when Repositories are the better choice.

14 min read

Magento 2.4.8 · PHP 8.4

GoF + Fowler Enterprise Pattern

Contents

1. 1. What is the Active Record Pattern?
2. 2. Magento's Adaptation: Model + ResourceModel
3. 3. AbstractModel: Data Without DB Logic
4. 4. ResourceModel: The Database Layer
5. 5. CRUD Operations in Detail
6. 6. Events and Before/After Hooks
7. 7. Building Your Own Model + ResourceModel
8. 8. Repository Pattern as a Modern Alternative
9. 9. Direct Model vs. Repository: When to Use What?
10. 10. Conclusion: Understanding and Replacing Active Record Properly

When Magento developers write $product->save(), they are using the Active Record Pattern. The model knows itself, its state, and how to persist itself to the database. Martin Fowler described

A freshly installed PHPStorm without a checklist costs hours: wrong interpreter, too much indexed vendor bulk, no Xdebug, no run configurations. This checklist covers all the critical settings, in the order that matters most for Docker Magento projects.

The category page is the most important performance hotspot in almost every Magento shop. Too many fields, resolver chains that run too deep, and missing caching strategies make it slower than it needs to be. The lever is in the query, not the server.

Headless commerce separates the Magento backend from a standalone frontend via a GraphQL API, whether that frontend is a PWA, a native app, or an IoT terminal. This article provides a concrete decision framework: when the extra complexity pays off through multi-channel requirements and separate teams, and when Hyva as a server-rendered default setup remains the faster and cheaper choice.

Redis is configured by default for maximum performance, not maximum security. Without authentication, with an open network bind and dangerous commands enabled, a production Redis instance becomes an easy target. This article shows the complete hardening process for Magento environments, from passwords and ACLs to TLS.

Wishlist functionality in the Hyvä Theme replaces Magento's Luma widgets with plain phtml and Alpine.js: an Alpine.store holds the product IDs of the saved list on the client, while fetch() calls against the Magento_Wishlist controller with form_key keep the server side in sync. This article shows how the heart icon reacts instantly to clicks, how optimistic updates with rollback work, and how guests are guided cleanly to login without a single page ever fully reloading.

Anyone integrating a third-party module into a Hyva theme sooner or later runs into the module-config.json file. It decides, per module, whether native Hyva templates apply or whether the frontend output falls back to a fallback theme like Magento/blank. This article explains the structure, runtime logic, merge behavior, and custom entries of module-config.json step by step.

A React product configurator for Magento has to manage attribute combinations, live price calculation and stock in real time without slowing down across hundreds of variants. The right state model decides whether the configurator feels instantly responsive or noticeably lags on every click.

Magento GraphQL resolvers implement a simple, well-defined interface that can be tested directly with PHPUnit, without ever building the complete schema, once field resolution and data fetching are cleanly separated.