PHP

A grown PHP monolith can rarely be replaced in one big leap. Legacy PHP code can, however, be modernized in a controlled way if you identify seams, write characterization tests and gradually wrap the old code using the Strangler Fig pattern instead of replacing it in one risky rewrite.

Running OPcache, Redis, Varnish and a CDN without a clear division of responsibility produces inconsistent load times and hard to reproduce bugs caused by stale data. This article explains how each layer solves a distinct problem, how invalidation works reliably across tags and TTLs, and how request locking and probabilistic early renewal prevent cache stampedes from overwhelming the origin.

The decorator pattern solves a problem that plain inheritance cannot cleanly solve: combining several independent additional behaviors, for example logging, caching and validation, flexibly and in any order, without building a separate subclass for every combination. This article shows how the decorator pattern in PHP preserves interface conformance and when it is preferable to inflating inheritance hierarchies.

Hot reload behaves differently in containers than on bare metal, because bind mounts, filesystem events and OPcache validation add extra layers between the editor and the running process. Understanding these layers makes PHP and Node changes appear just as fast as without containers, without rebuilding on every code change.

PHPUnit 10 replaced the long-grown TestListener with a cleanly typed Extension API. Anyone who wants custom logging, Slack notifications on failure, or project-specific rules inside their test suite will find the migration path here, with runnable examples.

strlen() counts bytes, not characters, and returns wrong values for umlauts and Unicode characters almost every time. This guide explains how UTF-8 encoding works, why mb_ functions are essential for multibyte strings, and how truncation, sorting, escaping and regular expressions with umlauts work reliably in PHP 8.4.

DateTime objects can be changed after creation, and that is exactly what produces hard-to-find bugs in larger codebases. DateTimeImmutable solves this problem structurally by having every method return a new instance instead of changing the existing object. This article shows, with real PHP 8.4 code, how DateTimeImmutable, DateTimeZone and DateInterval work together, and how existing DateTime code can be migrated.

Distroless images contain neither a shell nor a package manager nor unnecessary system libraries, which drastically reduces the attack surface of a PHP container. With static-php-cli or FrankenPHP as a base, a complete PHP runtime can be compiled into a distroless image without needing the classic PHP-FPM distribution.

PHPStorm supports three interpreter types: local, Docker/Docker Compose, and SSH. The choice has a direct impact on autocomplete quality, Xdebug reliability, and the overhead of starting run configurations. This article explains the differences and shows when which setup truly wins.

Not every PHP project is a monolith like Magento. For standalone microservices built with Symfony or Laravel, a much leaner .gitlab-ci.yml is enough, one that still cleanly covers the same core principles of build, test, and deployment.