Building stateless resolver with best practices (#1047)

2026年3月14日 12:13:50 Dave Brown

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 testing

登录发表评论

2 评论

Carol Williams 评论于 2026年3月14日 17:22

Abnobas sunt hilotaes de placidus vita. Silva de secundus galatae demitto quadra. Teres talis saepe tractare de camerarius flavum sensorem. Ut suscipit posuere justo at vulputate. Vae humani generis. Ubi est audax amicitia. Potus sensim ad ferox abnoba. Eros diam egestas libero eu vulputate risus. Pellentesque vitae velit ex. Sunt torquises imitari velox mirabilis medicinaes. Pellentesque et sapien pulvinar consectetur.

Grace Wilson 评论于 2026年3月14日 17:21

Ubi est audax amicitia. Nulla porta lobortis ligula vel egestas. Ut suscipit posuere justo at vulputate. Sunt torquises imitari velox mirabilis medicinaes.

这是一个使用Symfony框架构建的 示例应用 , 用以介绍开发Symfony应用的推荐方式.

了解更多信息, 请查看 Symfony 文档 .

点击按钮来展示渲染此页面的 Controller 控制器 和 Twig 模板 的源代码.

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