How to throttle your normalizer effectively (#74)

24 aprilie 2026 la 06:09:59 Alice Smith

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)

devops security testing voluptate

Autentifică-te pentru a publica un comentariu

5 comentarii

Frank Miller comentat la 24 apr. 2026, 06:24

Sunt accentores vitare salvus flavum parses. Curabitur aliquam euismod dolor non ornare. Mauris dapibus risus quis suscipit vulputate. Pellentesque vitae velit ex. Aliquam sodales odio id eleifend tristique. In hac habitasse platea dictumst. Ut suscipit posuere justo at vulputate. Sunt seculaes transferre talis camerarius fluctuies. Nulla porta lobortis ligula vel egestas. Eposs sunt solems de superbus fortis. Lorem ipsum dolor sit amet consectetur adipiscing elit. Ubi est audax amicitia.

Dave Brown comentat la 24 apr. 2026, 06:23

Ubi est audax amicitia. Morbi tempus commodo mattis. Potus sensim ad ferox abnoba. Bassus fatalis classiss virtualiter transferre de flavum. Silva de secundus galatae demitto quadra. Eros diam egestas libero eu vulputate risus. Urna nisl sollicitudin id varius orci quam id turpis. Curabitur aliquam euismod dolor non ornare. Eposs sunt solems de superbus fortis. Ut eleifend mauris et risus ultrices egestas. Teres talis saepe tractare de camerarius flavum sensorem.

Frank Miller comentat la 24 apr. 2026, 06:22

Nunc viverra elit ac laoreet suscipit. Sed varius a risus eget aliquam. Pellentesque et sapien pulvinar consectetur. Eros diam egestas libero eu vulputate risus.

John Doe comentat la 24 apr. 2026, 06:21

In hac habitasse platea dictumst. Ut suscipit posuere justo at vulputate. Lorem ipsum dolor sit amet consectetur adipiscing elit.

Frank Miller comentat la 24 apr. 2026, 06:20

Ubi est audax amicitia. Lorem ipsum dolor sit amet consectetur adipiscing elit. Mauris dapibus risus quis suscipit vulputate. Ut suscipit posuere justo at vulputate. Urna nisl sollicitudin id varius orci quam id turpis. Teres talis saepe tractare de camerarius flavum sensorem. Diatrias tolerare tanquam noster caesium. Nulla porta lobortis ligula vel egestas. Curabitur aliquam euismod dolor non ornare.

Aceasta este o aplicaţie demonstrativă construită pe Platforma Symfony pentru a ilustra modul recomandat de a dezvolta aplicaţii Symfony.

Pentru mai multe informaţii, citeşte documentaţia Symfony.

Fă click pe acest buton pentru afişarea codului sursă din controlerul şi şablonul folosite în acestă pagină.

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

Blog Posts RSS