Page 10 - Symfony

Symfony Messenger hides the actual queue behind a single DSN configuration, but underneath that abstraction sit fundamentally different backends with very different characteristics. Choosing Doctrine, Redis, or AMQP for a new project implicitly decides throughput limits, persistence guarantees in a crash, and the operational burden the team will carry going forward. This article compares the three common transport backends along exactly these three dimensions and shows which backend genuinely fits which use case.

Order processes, approval workflows, content publishing and ticket systems all have one thing in common: objects change their state according to defined rules. Implementing these transitions with if-constructs scattered across services builds up technical debt. The Symfony Workflow Component turns state machines into declarative configuration with full event support and visualization.

A REST API that runs in production but cannot be observed is a black box. Structured logging, distributed tracing with OpenTelemetry and Prometheus metrics are the three pillars that let teams localize errors, explain latency spikes and plan capacity, without digging through log files.

The Symfony Configuration Tree Builder is the tool a bundle uses to define which configuration is allowed, which values are mandatory and how invalid input is caught. This article walks through node types, default values, normalization and custom validation rules using a complete example.

Not every asynchronous requirement needs webhooks. Polling is sometimes the more sensible choice. And REST callbacks exist as a hybrid approach that many teams don't know about. Whoever understands the difference makes better architecture decisions, and doesn't build webhook infrastructure where a simple 30-second poll would be the cleaner solution.

Once a form needs to manage a variable number of similar sub-forms, for example line items on an order or tags on an article, a single field is no longer enough. CollectionType solves exactly this problem, but it requires allow_add/allow_delete, correct entity mapping, prototype-based JavaScript, and targeted PRE_SET_DATA and PRE_SUBMIT event listeners working together to be robust and secure.

The hexagonal architecture, also known as Ports and Adapters, frees the domain logic from coupling to frameworks, databases, and external services. In Symfony it can be implemented precisely with PHP interfaces as Ports and Symfony services as Adapters: fully testable domain code without a single framework import in the core logic.

A migration that spontaneously renames a column or locks a table can bring a running Symfony application to its knees right in the middle of rush hour. Zero downtime database migrations with Doctrine instead follow the expand contract pattern: schema and application grow through small, always backward compatible steps. This article walks through every step in detail, from the first new column to safely removing the old one.

The choice between EasyAdmin 4 and Sonata Admin determines how much configuration effort, customizing freedom and learning curve your team needs to plan for the backend. Both solutions are built for Symfony, but with fundamentally different philosophies and target audiences.

Anyone who thinks API Platform only works with Doctrine entities has not yet met the State Provider and the State Processor. These two interfaces fully decouple reading and writing from the persistence layer and let you expose REST endpoints, legacy systems, or purely computed values as first class API resources.