A growing exception.log is not monitoring, it is just a record. This article shows how Magento logs turn into a resilient log management and monitoring system: with custom Monolog handlers, central aggregation in Grafana Loki or ELK, alerting rules that avoid alert fatigue, and trace correlation across request boundaries.

A generic blue green deployment simply swaps two container versions. For Magento that is not enough, because indexers, cache, sessions and database migrations complicate the color switch. This article shows how blue green deployments for Magento in containers are built so the traffic switch actually happens without downtime and without inconsistent data.

POOL

♻️

Deep Dive · Magento 2 Design Patterns

Object Pool Pattern:
Reuse Objects Instead of Creating New Ones

How Magento pools DB connections, HTTP clients and resource-intensive objects internally, and how you can use the pattern for your own expensive initializations.

12 min read

Magento 2.4.8 · PHP 8.4

GoF Creational Pattern

Contents

1. 1. What is the Object Pool Pattern?
2. 2. When does pooling make sense?
3. 3. PHP 8.4 implementation
4. 4. Magento: the DB connection pool (ResourceConnection)
5. 5. HTTP client pool in Magento
6. 6. Building your own pool: a PDF generator example
7. 7. PHP request scope: why classic pooling is limited
8. 8. Pool vs. Singleton vs. Factory
9. 9. Testing object pools
10. 10. Conclusion: when to use Object Pool in Magento

The Object Pool Pattern is one of the often overlooked Creational Patterns from the GoF catalog. The idea is simple: instead of creating and destroying an expensive object every time, you build up a stock (pool) of such objects

Magento 2 needs a precisely tuned service stack. PHP-FPM, Nginx, MariaDB, Redis, Elasticsearch or OpenSearch, and a Node container for frontend builds: each of these services has specific configuration requirements that differ in Docker from a classic server installation. Knowing these differences is what lets you build a stable and performant Magento Docker stack.

Magento 2 · Service Contracts

Mastering SearchCriteria
AND/OR Filters, Pagination, Sorting

At first glance, SearchCriteria in Magento 2 looks generic and simple. In practice, though, many implementations fail because of FilterGroup logic, wrong assumptions about AND and OR, or repository queries that are more accidental than the result of deliberate query design.

18 min read Repositories Magento 2.4.8

Table of Contents

1. 1. What SearchCriteria in Magento 2 actually is
2. 2. Understanding AND and OR in SearchCriteria correctly
3. 3. Using pagination and page sizes cleanly
4. 4. Controlling sorting deliberately with SortOrder
5. 5. SearchCriteria in repository practice
6. 6. Common mistakes
7. 7. SearchCriteria vs. direct Collection
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What SearchCriteria in Magento 2 actually is

SearchCriteria Magento 2 is the standardized language repositories use to describe list queries. Instead of thinking directly in terms of collections

In Magento 2 there are three fundamentally different test types with very different runtimes, maintenance costs, and areas of use. PHPUnit for unit and integration tests, MFTF for end-to-end browser tests, and REST API tests for the web service layer. The most common mistakes in Magento test strategies: too many MFTF tests, too few unit tests, and API tests that should really be logic tests.

After every Magento deployment the Redis cache is empty, and the first requests hit the database unchecked. This article explains why that traffic spike happens, how warmup crawlers and cache preload scripts prevent it, and how warmup can be cleanly integrated into a deployment pipeline.

Declarative Schema replaces old InstallScripts, but only when tables, constraints, indexes, and patches are kept cleanly separated. These five mistakes cause most of the problems in Magento projects.

An undersized Redis server leads to frequent eviction, dropping hit rates, and in the worst case out of memory errors right in the middle of checkout. Proper memory sizing means realistically estimating the memory needs of cache, session and full page cache based on catalog size and traffic, instead of relying on roughly guessed defaults that account for neither growth nor traffic peaks.

Salable quantity in Magento MSI is not the physical stock on its own, it is stock minus reservations. Once that math goes off track because reservations linger even though the linked order was canceled or never paid, salable quantity drops artificially while nothing is physically missing. This article shows how such orphaned reservations happen, how to find them, and how a custom cleanup script restores consistency.