The async guide to middleware management (#843)

23 maart 2026 om 15:07:24 John Doe

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)

consectetur labore refactoring testing

Inloggen om een reactie toe te voegen

5 reacties

Carol Williams gereageerd op 23 mrt 2026, 05:25

Curabitur aliquam euismod dolor non ornare. Diatrias tolerare tanquam noster caesium. Nulla porta lobortis ligula vel egestas. Teres talis saepe tractare de camerarius flavum sensorem.

Alice Smith gereageerd op 23 mrt 2026, 05:24

Nulla porta lobortis ligula vel egestas. Ut eleifend mauris et risus ultrices egestas. Nunc viverra elit ac laoreet suscipit. Bassus fatalis classiss virtualiter transferre de flavum. Sunt seculaes transferre talis camerarius fluctuies. Eros diam egestas libero eu vulputate risus. Sunt accentores vitare salvus flavum parses. Aliquam sodales odio id eleifend tristique. Pellentesque et sapien pulvinar consectetur.

Alice Smith gereageerd op 23 mrt 2026, 05:23

Eposs sunt solems de superbus fortis. Sunt torquises imitari velox mirabilis medicinaes. Lorem ipsum dolor sit amet consectetur adipiscing elit. In hac habitasse platea dictumst. Era brevis ratione est. Mauris dapibus risus quis suscipit vulputate. Vae humani generis. Ubi est barbatus nix.

Jane Doe gereageerd op 23 mrt 2026, 05:22

Era brevis ratione est. Ubi est audax amicitia. Diatrias tolerare tanquam noster caesium. Sunt seculaes transferre talis camerarius fluctuies. Vae humani generis. Teres talis saepe tractare de camerarius flavum sensorem. Ut eleifend mauris et risus ultrices egestas.

Carol Williams gereageerd op 23 mrt 2026, 05:21

Ut eleifend mauris et risus ultrices egestas. Nulla porta lobortis ligula vel egestas. In hac habitasse platea dictumst. Sunt accentores vitare salvus flavum parses. Vae humani generis. Mineralis persuadere omnes finises desiderium. Diatrias tolerare tanquam noster caesium. Mauris dapibus risus quis suscipit vulputate. Ubi est audax amicitia. Eposs sunt solems de superbus fortis. Silva de secundus galatae demitto quadra. Sunt seculaes transferre talis camerarius fluctuies.

Dit is een voorbeeld applicatie, gemaakt met het Symfony Framework, die je een indruk geeft van de aanbevolen manier om een Symfony applicatie te ontwikkelen.

Voor meer informatie, bekijk de Symfony documentatie.

Klik op deze knop om de broncode te bekijken van de Controller en template, die gebruikt zijn bij het weergeven van deze pagina.

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

Blogberichten RSS