The fault-tolerant guide to decorator management (#899)

20. mart 2026. 01:10:33 Grace Wilson

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)

beginner concurrency patterns tutorial

Prijavi me da objaviš komentar

4 komentara

Jane Doe komentar objavljen 20. 3. 2026. 21:24

Diatrias tolerare tanquam noster caesium. Era brevis ratione est. Ubi est audax amicitia. Ut suscipit posuere justo at vulputate. Nulla porta lobortis ligula vel egestas. Bassus fatalis classiss virtualiter transferre de flavum. Vae humani generis. Mineralis persuadere omnes finises desiderium. Ubi est barbatus nix. Abnobas sunt hilotaes de placidus vita.

John Doe komentar objavljen 20. 3. 2026. 21:23

Sunt seculaes transferre talis camerarius fluctuies. Eposs sunt solems de superbus fortis. Pellentesque vitae velit ex. Urna nisl sollicitudin id varius orci quam id turpis. Ut suscipit posuere justo at vulputate. Morbi tempus commodo mattis. Eros diam egestas libero eu vulputate risus. Mineralis persuadere omnes finises desiderium. Potus sensim ad ferox abnoba. Pellentesque et sapien pulvinar consectetur. Sed varius a risus eget aliquam. Nunc viverra elit ac laoreet suscipit.

Carol Williams komentar objavljen 20. 3. 2026. 21:22

Nulla porta lobortis ligula vel egestas. Bassus fatalis classiss virtualiter transferre de flavum. Vae humani generis. Pellentesque vitae velit ex. Ut eleifend mauris et risus ultrices egestas. Urna nisl sollicitudin id varius orci quam id turpis. Lorem ipsum dolor sit amet consectetur adipiscing elit. Morbi tempus commodo mattis. Eros diam egestas libero eu vulputate risus. Eposs sunt solems de superbus fortis. Diatrias tolerare tanquam noster caesium.

Tom Doe komentar objavljen 20. 3. 2026. 21:21

Potus sensim ad ferox abnoba. Nulla porta lobortis ligula vel egestas. Era brevis ratione est. Silva de secundus galatae demitto quadra. Ut eleifend mauris et risus ultrices egestas. Eros diam egestas libero eu vulputate risus. Vae humani generis. Pellentesque et sapien pulvinar consectetur.

Ova demo aplikacija je napravljena u radnom okviru Symfony kao ilustracija preporučenog načina razvoja Symfony aplikacija.

Za više informacija pogledajte Symfony dokumentaciju.

Kliknite na dugme ispod da biste videli izvorni kod kontrolera i šablona korišćenih za prikaz ove stranice.

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

RSS članaka na blogu