Building async middleware with best practices (#623)

1 de abril de 2026, 8:57:02 Bob Johnson

Architecture Decisions

Every system is the sum of its architectural decisions. Some decisions are reversible (which framework to use), others are irreversible (which database engine to choose). Focus your deliberation accordingly.

The Monolith-First Approach

Start with a well-structured monolith. Extract services only when you have:

Clear bounded contexts
Independent scaling requirements
Team boundaries that align with service boundaries

Event-Driven Communication

Instead of synchronous HTTP calls between services:

Service A → Message Bus → Service B
                        → Service C
                        → Service D

Benefits:

Decoupling: Services don't need to know about each other
Resilience: Failed consumers retry independently
Scalability: Add consumers without changing producers

Data Ownership

Each service owns its data. No shared databases. If Service B needs data from Service A, it either:

Subscribes to Service A's events and maintains a local projection
Makes an API call (with caching and circuit breakers)
Uses a shared read model (CQRS pattern)

incididunt refactoring symfony

Iniciar sesión para publicar un comentario

2 comentarios

John Doe comentado el 1 abr 2026, 9:22

Potus sensim ad ferox abnoba. Ut eleifend mauris et risus ultrices egestas. Pellentesque et sapien pulvinar consectetur. Nunc viverra elit ac laoreet suscipit. Eros diam egestas libero eu vulputate risus. Sunt seculaes transferre talis camerarius fluctuies. Sed varius a risus eget aliquam. Ubi est audax amicitia. Vae humani generis.

Frank Miller comentado el 1 abr 2026, 9:21

Diatrias tolerare tanquam noster caesium. Sunt accentores vitare salvus flavum parses. Eros diam egestas libero eu vulputate risus. Ut eleifend mauris et risus ultrices egestas.

Esta aplicación demo ha sido programada con el framework Symfony para mostrar la forma recomendada de programar aplicaciones Symfony.

Para más información, consulta la documentación de Symfony.

Pulsa este botón para ver el código fuente del controlador y de la plantilla utilizados para crear esta página.

src/Controller/BlogController.php at line 272

/**
 * NOTE: when the controller argument is a Doctrine entity, Symfony makes an
 * automatic database query to fetch it based on the value of the route parameters.
 * The '{slug:post}' configuration tells Symfony to use the 'slug' route
 * parameter in the database query that fetches the entity of the $post argument.
 * This is mostly useful when the route has multiple parameters and the controller
 * also has multiple arguments.
 * See https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver.
 */
#[Route('/posts/{slug:post}', name: 'blog_post', requirements: ['slug' => Requirement::ASCII_SLUG], methods: ['GET'])]
public function postShow(Post $post): Response
{
    // Symfony's 'dump()' function is an improved version of PHP's 'var_dump()' but
    // it's not available in the 'prod' environment to prevent leaking sensitive information.
    // It can be used both in PHP files and Twig templates, but it requires to
    // have enabled the DebugBundle. Uncomment the following line to see it in action:
    //
    // dump($post, $this->getUser(), new \DateTime());
    //
    // The result will be displayed either in the Symfony Profiler or in the stream output.
    // See https://symfony.com/doc/current/profiler.html
    // See https://symfony.com/doc/current/templates.html#the-dump-twig-utilities
    //
    // You can also leverage Symfony's 'dd()' function that dumps and
    // stops the execution

    return $this->render('blog/post_show.html.twig', ['post' => $post]);
}

templates/blog/post_show.html.twig at line 1

RSS del blog