Why every developer should containerize compiler (#788)

25 maart 2026 om 07:05:58 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)

consectetur lorem php

Inloggen om een reactie toe te voegen

5 reacties

Jane Doe gereageerd op 25 mrt 2026, 12:25

In hac habitasse platea dictumst. Potus sensim ad ferox abnoba. Era brevis ratione est.

Jane Doe gereageerd op 25 mrt 2026, 12:24

Lorem ipsum dolor sit amet consectetur adipiscing elit. Mineralis persuadere omnes finises desiderium. Ut suscipit posuere justo at vulputate. Mauris dapibus risus quis suscipit vulputate. Curabitur aliquam euismod dolor non ornare. Diatrias tolerare tanquam noster caesium. Ut eleifend mauris et risus ultrices egestas. Ubi est audax amicitia. Sunt seculaes transferre talis camerarius fluctuies. Pellentesque vitae velit ex. Sed varius a risus eget aliquam.

Alice Smith gereageerd op 25 mrt 2026, 12:23

Eros diam egestas libero eu vulputate risus. Nulla porta lobortis ligula vel egestas. Ut suscipit posuere justo at vulputate. Sunt accentores vitare salvus flavum parses. Morbi tempus commodo mattis. Curabitur aliquam euismod dolor non ornare. Ubi est barbatus nix. In hac habitasse platea dictumst. Eposs sunt solems de superbus fortis. Sed varius a risus eget aliquam.

Bob Johnson gereageerd op 25 mrt 2026, 12:22

Diatrias tolerare tanquam noster caesium. Curabitur aliquam euismod dolor non ornare. Pellentesque et sapien pulvinar consectetur. Mineralis persuadere omnes finises desiderium. Silva de secundus galatae demitto quadra. Ubi est audax amicitia. Nulla porta lobortis ligula vel egestas. In hac habitasse platea dictumst. Sunt accentores vitare salvus flavum parses. Potus sensim ad ferox abnoba. Sunt seculaes transferre talis camerarius fluctuies.

Dave Brown gereageerd op 25 mrt 2026, 12:21

Silva de secundus galatae demitto quadra. Morbi tempus commodo mattis. Sunt torquises imitari velox mirabilis medicinaes.

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