Page 2 - Symfony

A user registers, the welcome email must be sent asynchronously, the CRM entry created, and the analytics updated. At the same time, the domain should fire an event that reacts synchronously to the same process. Symfony Messenger and the Event Dispatcher can both do this, once you understand how they work together.

Arrays as request and response data containers are the most common maintenance problem in Symfony REST APIs: no type safety, no autocompletion, no documentation generated from the code. PHP 8.4 readonly properties, the Symfony Serializer and the Symfony Validator turn DTOs into a clear upgrade, with less code, more safety and better IDE support.

Symfony UX Dropzone turns an ordinary file field into a modern drag-and-drop zone with image previews, without requiring a custom upload handler written in JavaScript, and combines directly with VichUploaderBundle and your own validation rules.

An unstructured OpenAPI specification turns into a maintenance burden the moment more than three developers work on it. With components/schemas, consistent $ref references and a clear versioning strategy, the API description stays the single source of truth for documentation, code generation and contract tests.

WebTestCase only simulates a browser based on the returned HTML and never executes a single line of JavaScript, which means it simply tests nothing for Stimulus controllers, Symfony UX Live Components, or Turbo interactions. Symfony Panther closes this gap by driving a real Chrome or Firefox process through the WebDriver protocol. This article covers when the switch pays off, how waiting and screenshot debugging work, and what performance tradeoffs come with it.

Insecure REST APIs are not a rare occurrence. They do not arise from bad intentions but from missing security layers in a growing codebase. Authentication gaps, missing rate limiting, unvalidated input, SSRF vectors and mass assignment weaknesses are the most common findings in API security reviews, and they can be closed systematically with clear patterns.

Every public API has to change eventually. The question is not whether, but how, without breaking existing clients. API versioning is not a pure architecture decision, it is an operational process: from the URI strategy through content negotiation to structured deprecation cycles, the strategy determines how much technical debt an API accumulates over time.

How to use a custom Doctrine DBAL type to work with a Money object or an EmailAddress value object directly in entities, including convertToPHPValue, convertToDatabaseValue, and registration.

Symfony is the most robust PHP framework for complex backend logic. React is the most powerful UI framework for dynamic frontends. API Platform connects the two through automatically generated REST and GraphQL APIs, complete with validation, serialization and OpenAPI documentation out of the box. This article shows how to bring the two worlds together in a production ready way.

Anyone who has registered event listeners in Symfony via services.yaml with tags and method names knows the pain of maintaining several files for a single class. The PHP attribute #[AsEventListener] eliminates this YAML configuration entirely, the listener is declared directly on the class or method, type-safe and immediately readable.