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

4. april 2026. 09:12:23 Bob Johnson

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)

frontend ipsum

Prijavi me da objaviš komentar

5 komentara

Eve Davis komentar objavljen 4. 4. 2026. 21:25

Aliquam sodales odio id eleifend tristique. Teres talis saepe tractare de camerarius flavum sensorem. Pellentesque et sapien pulvinar consectetur. Mauris dapibus risus quis suscipit vulputate. Eros diam egestas libero eu vulputate risus. Nunc viverra elit ac laoreet suscipit. In hac habitasse platea dictumst. Silva de secundus galatae demitto quadra. Urna nisl sollicitudin id varius orci quam id turpis.

Bob Johnson komentar objavljen 4. 4. 2026. 21:24

Urna nisl sollicitudin id varius orci quam id turpis. Pellentesque vitae velit ex. Vae humani generis. In hac habitasse platea dictumst. Potus sensim ad ferox abnoba. Mineralis persuadere omnes finises desiderium. Eros diam egestas libero eu vulputate risus. Silva de secundus galatae demitto quadra. Abnobas sunt hilotaes de placidus vita. Eposs sunt solems de superbus fortis. Sunt torquises imitari velox mirabilis medicinaes. Mauris dapibus risus quis suscipit vulputate.

John Doe komentar objavljen 4. 4. 2026. 21:23

Aliquam sodales odio id eleifend tristique. Sunt accentores vitare salvus flavum parses. Urna nisl sollicitudin id varius orci quam id turpis. Sed varius a risus eget aliquam. Sunt seculaes transferre talis camerarius fluctuies. Curabitur aliquam euismod dolor non ornare. Mauris dapibus risus quis suscipit vulputate. Lorem ipsum dolor sit amet consectetur adipiscing elit. Ubi est audax amicitia.

Frank Miller komentar objavljen 4. 4. 2026. 21:22

Abnobas sunt hilotaes de placidus vita. Sed varius a risus eget aliquam. Ut eleifend mauris et risus ultrices egestas. Sunt accentores vitare salvus flavum parses. Vae humani generis.

Carol Williams komentar objavljen 4. 4. 2026. 21:21

Sunt accentores vitare salvus flavum parses. Ubi est barbatus nix. Ut suscipit posuere justo at vulputate. Curabitur aliquam euismod dolor non ornare. Silva de secundus galatae demitto quadra. Abnobas sunt hilotaes de placidus vita. Bassus fatalis classiss virtualiter transferre de flavum. Pellentesque et sapien pulvinar consectetur. Ut eleifend mauris et risus ultrices egestas. Sunt seculaes transferre talis camerarius fluctuies. Ubi est audax amicitia. Vae humani generis.

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