The async guide to middleware management (#243)

17 april 2026 om 21:44:27 Frank Miller

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)

beginner consectetur devops pariatur refactoring

Inloggen om een reactie toe te voegen

4 reacties

Dave Brown gereageerd op 17 apr 2026, 05:24

Vae humani generis. Aliquam sodales odio id eleifend tristique. Pellentesque vitae velit ex. Silva de secundus galatae demitto quadra. Mineralis persuadere omnes finises desiderium. Sunt seculaes transferre talis camerarius fluctuies. Mauris dapibus risus quis suscipit vulputate. Bassus fatalis classiss virtualiter transferre de flavum. Sed varius a risus eget aliquam. In hac habitasse platea dictumst. Potus sensim ad ferox abnoba.

Alice Smith gereageerd op 17 apr 2026, 05:23

Silva de secundus galatae demitto quadra. Ut eleifend mauris et risus ultrices egestas. Eros diam egestas libero eu vulputate risus. Era brevis ratione est. Sed varius a risus eget aliquam. Teres talis saepe tractare de camerarius flavum sensorem. Bassus fatalis classiss virtualiter transferre de flavum. Curabitur aliquam euismod dolor non ornare. Mineralis persuadere omnes finises desiderium. Pellentesque et sapien pulvinar consectetur. Aliquam sodales odio id eleifend tristique.

Bob Johnson gereageerd op 17 apr 2026, 05:22

Ubi est audax amicitia. Mineralis persuadere omnes finises desiderium. Ut eleifend mauris et risus ultrices egestas. Sed varius a risus eget aliquam. Urna nisl sollicitudin id varius orci quam id turpis. Mauris dapibus risus quis suscipit vulputate. Teres talis saepe tractare de camerarius flavum sensorem. Sunt torquises imitari velox mirabilis medicinaes. In hac habitasse platea dictumst.

Frank Miller gereageerd op 17 apr 2026, 05:21

Sunt seculaes transferre talis camerarius fluctuies. Ut suscipit posuere justo at vulputate. Teres talis saepe tractare de camerarius flavum sensorem.

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