Building stateless resolver with best practices (#647)

31. март 2026. 05:56:39 John Doe

Understanding the Problem

When building modern web applications, performance is not just a feature — it's a requirement. Users expect sub-second response times, and search engines penalize slow pages. This post explores practical techniques for optimization.

Key Metrics

Time to First Byte (TTFB)
Largest Contentful Paint (LCP)
Cumulative Layout Shift (CLS)

"Premature optimization is the root of all evil" — Donald Knuth

However, measured optimization based on profiling data is the root of all performance gains. Let's look at real-world examples.

Database Optimization

-- Before: full table scan
SELECT * FROM posts WHERE status = 'published' ORDER BY created_at DESC;

-- After: indexed query with pagination
SELECT id, title, summary FROM posts
WHERE status = 'published'
ORDER BY created_at DESC
LIMIT 20 OFFSET 0;

The difference? From 850ms to 12ms on a table with 500K rows.

Caching Strategy

Use a multi-layer cache:

L1: In-memory (APCu) — microsecond access
L2: Redis — millisecond access
L3: Database — last resort

Each layer has different TTLs and invalidation strategies.

beginner refactoring

Пријави ме да објавиш коментар

3 коментара

John Doe коментар објављен 31. 3. 2026. 09:23

Nunc viverra elit ac laoreet suscipit. Aliquam sodales odio id eleifend tristique. Pellentesque et sapien pulvinar consectetur. Sunt accentores vitare salvus flavum parses.

Alice Smith коментар објављен 31. 3. 2026. 09:22

Urna nisl sollicitudin id varius orci quam id turpis. Eros diam egestas libero eu vulputate risus. Sunt seculaes transferre talis camerarius fluctuies.

Grace Wilson коментар објављен 31. 3. 2026. 09:21

Pellentesque et sapien pulvinar consectetur. Eros diam egestas libero eu vulputate risus. Ut eleifend mauris et risus ultrices egestas.

Ова демо апликација је направљена у радном оквиру Symfony као илустрација препорученог начина развоја Symfony aпликација.

За више информација погледајте Symfony документацију.

Кликните на дугме испод да бисте видели изворни код контролера и шаблона коришћених за приказ ове странице.

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 чланака на блогу