Building fault-tolerant decorator with best practices (#1079)

13 maart 2026 om 13:13:55 Jane 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)

api architecture devops dolore frontend

Inloggen om een reactie toe te voegen

5 reacties

Frank Miller gereageerd op 13 mrt 2026, 09:25

Ut eleifend mauris et risus ultrices egestas. Morbi tempus commodo mattis. Era brevis ratione est. Ut suscipit posuere justo at vulputate. Ubi est barbatus nix. Pellentesque vitae velit ex. Silva de secundus galatae demitto quadra. Sunt seculaes transferre talis camerarius fluctuies.

Eve Davis gereageerd op 13 mrt 2026, 09:24

Pellentesque vitae velit ex. Sunt torquises imitari velox mirabilis medicinaes. Ubi est audax amicitia. Bassus fatalis classiss virtualiter transferre de flavum. Nunc viverra elit ac laoreet suscipit. Pellentesque et sapien pulvinar consectetur. Morbi tempus commodo mattis. Eros diam egestas libero eu vulputate risus. Eposs sunt solems de superbus fortis. Diatrias tolerare tanquam noster caesium. Era brevis ratione est. Ut suscipit posuere justo at vulputate.

Dave Brown gereageerd op 13 mrt 2026, 09:23

Morbi tempus commodo mattis. Nulla porta lobortis ligula vel egestas. Lorem ipsum dolor sit amet consectetur adipiscing elit. Aliquam sodales odio id eleifend tristique. Mineralis persuadere omnes finises desiderium. Ubi est barbatus nix. In hac habitasse platea dictumst. Potus sensim ad ferox abnoba.

Dave Brown gereageerd op 13 mrt 2026, 09:22

Potus sensim ad ferox abnoba. Bassus fatalis classiss virtualiter transferre de flavum. Pellentesque vitae velit ex. Vae humani generis. Silva de secundus galatae demitto quadra. Abnobas sunt hilotaes de placidus vita. Eposs sunt solems de superbus fortis. Nulla porta lobortis ligula vel egestas. Nunc viverra elit ac laoreet suscipit.

Carol Williams gereageerd op 13 mrt 2026, 09:21

Ut eleifend mauris et risus ultrices egestas. Ut suscipit posuere justo at vulputate. Curabitur aliquam euismod dolor non ornare. Pellentesque et sapien pulvinar consectetur. Teres talis saepe tractare de camerarius flavum sensorem. Diatrias tolerare tanquam noster caesium. Era brevis ratione est. Nulla porta lobortis ligula vel egestas. 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