Articles
Event-driven architecture, CI/CD, identity and Symfony: what we recommend, and why.
Event-driven architecture
Splitting an event-driven architecture: six axes to decide
Data ownership, messages, transport, push to the fronts, shared code, transactions: the six axes of an event-driven architecture, a services map and procedures.
11 min read
Real time with Mercure, no BFF: domains, cookies and JWTs
Pushing order updates to Vue fronts without a BFF: a Mercure 1.0 hub, a cookie on the parent domain and one restricted publisher token for each service.
11 min read
Kafka or RabbitMQ? Keep RabbitMQ and replay from the outbox
Replaying events without moving to Kafka: the outbox, kept for a long time, becomes a log that we republish to the queue of a single RabbitMQ consumer.
11 min read
Dead letter queues with RabbitMQ and Symfony Messenger
A message that fails forever clogs its queue. Retries with a growing delay, then quarantine: Messenger failure transport or RabbitMQ DLX, two distinct levels.
4 min read
Message contracts in a monorepo: JSON Schema and DTOs
In a monorepo, a message change passes the tests, then breaks in production. A shared contracts package, additive changes and frozen fixtures prevent it.
11 min read
Idempotent consumer with Symfony Messenger: the processed_event table
The same event can arrive twice. A processed_event table, written in the same transaction as the effect, discards the duplicate with Symfony Messenger.
11 min read
The Outbox pattern with Symfony Messenger: publish without losing events
Writing to the database then publishing can lose an event. The outbox writes it in the same transaction, a relay publishes it: Messenger, Doctrine, PostgreSQL.
11 min read
RabbitMQ: one topic exchange and one queue per consuming service
Several services react to the same event? A single topic exchange, one queue per consuming service and versioned routing keys, with Symfony Messenger.
9 min read
Industrialization
Production secrets: take them out of the forge with Dokploy
The Git forge is read by more people than production. With Dokploy, each environment holds its own secrets: the CI never sees them and holds no Dokploy key.
11 min read
Build once, promote many: deploying by digest with Dokploy
One image per commit, built and scanned once, promoted by digest: a job placed inside each isolated environment calls the API of its own Dokploy instance.
11 min read
CI supply chain: pin your tools and produce an SBOM
Actions pinned by commit SHA, images by digest, tools by checksum, dependencies through a proxy: secure the CI and ship every image signed, with its SBOM.
11 min read
Thin CI pipelines driven by moon in a monorepo
In a monorepo, moon decides what to test while the CI orchestrates: a thin YAML, the same tasks run locally and a sound comparison base, never HEAD~1.
11 min read
Symfony code quality with free tools: PHPStan, Rector, Deptrac
SonarQube Community Build does not analyse pull requests. PHPStan, PHP-CS-Fixer, Rector and Deptrac, run by moon, check them free of charge in a monorepo.
11 min read
Identity and access
APIs and Symfony
API Platform: a readable ComparisonFilter in OpenAPI
Up to 4.4.2, ComparisonFilter documents each operator as an object, then as a string. Type them with openApi, validate with constraints, avoid the schema trap.
4 min read
API Platform and ObjectMapper: the pitfalls of DTO resources
#[Map] ignored without a source, relations, genid IRIs, a PATCH that erases a field. The ObjectMapper pitfalls with API Platform 4.4 and 5.0, checked in code.
11 min read
FrankenPHP in Docker: no more root-owned files
On Linux, files generated in the FrankenPHP dev container belong to root. A non-root Docker stage, built with the host UID and GID, fixes the problem.
4 min read
API Platform: separate Doctrine entities from API resources
Exposing Doctrine entities ties the database to the API contract. DTO resources, stateOptions and explicit providers keep pagination, filters and extensions.
11 min read