composable optimizer: a deep dive into modern practices (#1089)

12 maart 2026 om 17:53:20 Tom Doe

Testing in Production

Yes, you read that right. Testing in production — not instead of staging, but in addition to it. Here's why and how.

Why Staging Lies

Staging environments differ from production in subtle but critical ways:

Different data volumes (10K rows vs 10M rows)
Different traffic patterns (no real users)
Different infrastructure (smaller instances)
Different integrations (sandbox APIs)

Canary Deployments

Route a small percentage of traffic to the new version:

# nginx.conf
upstream backend {
    server app-v1:8080 weight=95;
    server app-v2:8080 weight=5;
}

Monitor error rates, latency percentiles, and business metrics. If anything degrades, roll back automatically.

Feature Flags

Decouple deployment from release:

Deploy code to 100% of servers
Enable feature for 1% of users
Gradually increase to 5%, 25%, 100%
Kill switch: disable instantly without redeployment

Observability

You can't test what you can't see. Invest in:

Structured logging (JSON, correlation IDs)
Distributed tracing (OpenTelemetry)
Custom metrics (business KPIs, not just CPU/memory)
Alerting (on symptoms, not causes)

database devops patterns php

Inloggen om een reactie toe te voegen

5 reacties

Tom Doe gereageerd op 12 mrt 2026, 23:25

Bassus fatalis classiss virtualiter transferre de flavum. Silva de secundus galatae demitto quadra. Pellentesque vitae velit ex. Morbi tempus commodo mattis. Curabitur aliquam euismod dolor non ornare. Sed varius a risus eget aliquam. Mineralis persuadere omnes finises desiderium. Eposs sunt solems de superbus fortis. Nunc viverra elit ac laoreet suscipit. Aliquam sodales odio id eleifend tristique. Ut eleifend mauris et risus ultrices egestas.

Alice Smith gereageerd op 12 mrt 2026, 23:24

Urna nisl sollicitudin id varius orci quam id turpis. Lorem ipsum dolor sit amet consectetur adipiscing elit. Eros diam egestas libero eu vulputate risus.

Grace Wilson gereageerd op 12 mrt 2026, 23:23

Mineralis persuadere omnes finises desiderium. Curabitur aliquam euismod dolor non ornare. Nunc viverra elit ac laoreet suscipit. In hac habitasse platea dictumst. Lorem ipsum dolor sit amet consectetur adipiscing elit. Sunt seculaes transferre talis camerarius fluctuies. Aliquam sodales odio id eleifend tristique. Eros diam egestas libero eu vulputate risus.

Dave Brown gereageerd op 12 mrt 2026, 23:22

Mauris dapibus risus quis suscipit vulputate. Urna nisl sollicitudin id varius orci quam id turpis. In hac habitasse platea dictumst. Diatrias tolerare tanquam noster caesium. Abnobas sunt hilotaes de placidus vita. Ut eleifend mauris et risus ultrices egestas. Mineralis persuadere omnes finises desiderium. Pellentesque vitae velit ex.

Jane Doe gereageerd op 12 mrt 2026, 23:21

Diatrias tolerare tanquam noster caesium. Bassus fatalis classiss virtualiter transferre de flavum. Silva de secundus galatae demitto quadra. Ubi est audax amicitia. Ut suscipit posuere justo at vulputate. Eros diam egestas libero eu vulputate risus. In hac habitasse platea dictumst. Sunt accentores vitare salvus flavum parses.

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