Symfony

Most applications end up with three or four separate libraries for notifications: one for email, one for Slack, one for SMS, one for push notifications. Symfony Notifier unifies every channel behind a single interface and a single dispatch method, with configurable routing, channel-specific messages and the ability to write your own bridges for internal systems.

A Stimulus controller only shows its real strength once lifecycle callbacks, targets, values and outlets are used deliberately, instead of hunting down every DOM element with querySelector, and these exact building blocks turn scattered jQuery fragments into maintainable, testable frontend pieces in Symfony projects.

How to build fixture classes with references between entities using the DoctrineFixturesBundle, separate fixture groups for dev and test, and generate realistic test data with Faker.

Symfony as the backend framework, API Platform as the REST layer and React as the frontend form a stack where every layer plays to its strengths. The result: a type-safe fullstack application where the TypeScript client is generated from the OpenAPI schema and JWT authentication is cleanly integrated into both layers.

Webhooks from Stripe, GitHub, Shopify or your own services arrive as HTTP POST requests, without type safety, without schema guarantees, and potentially from spoofed senders. Symfony offers a complete infrastructure with the Webhook component, Messenger and HMAC signature verification to process external events safely, type-safely and asynchronously.

Primitive obsession, meaning representing business concepts as bare strings and integers, is one of the most common sources of unclear domain code. Embeddables turn value objects like Money or Address into first class citizens in Doctrine mapping, without requiring their own database tables.

API Platform generates OpenAPI documentation from PHP classes, which saves hours of manual work. But schema names with internal counters, missing examples, rudimentary security definitions and undocumented error cases show where the automation promise reaches its limits. This article shows concretely what works well, and what needs to be overridden.

Once an application processes messages asynchronously through Symfony Messenger, a failing message is not the exception, it is the normal case: an external service becomes briefly unavailable, a database connection drops, or a worker gets restarted mid-processing. Anyone who blindly trusts the default settings either loses messages because they are given up on too early, or overloads an already struggling system with retries that fire too often. This article explains exactly how Messenger's retry strategy works, how the failed transport acts as a second safety net, and how to configure both mechanisms deliberately for a real use case.

Why a real DELETE is often the wrong choice for referenced data, and how to build a robust soft delete pattern with a Doctrine filter, a deletedAt column, and clean unique constraints.

Many REST APIs use HTTP as a transport protocol without ever tapping into its semantics. Resources modeled incorrectly, verbs misused, idempotency not guaranteed and status codes chosen arbitrarily, these are not questions of style but design errors with direct consequences for caching, retry logic and client implementation.