--- title: Issue #633: The life of a ~200ms HTTP request to a Node... description: Node Weekly issue #633 covers a scroll-driven visualization tracing every step of a ~200ms HTTP POST request through Node's internals and event loop, a... canonical: https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Issue #633: The life of a ~200ms HTTP request to a Node app — Node Weekly | daily.dev og:description: Node Weekly issue #633 covers a scroll-driven visualization tracing every step of a ~200ms HTTP POST request through Node's internals and event loop, a... og:url: https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt og:image: https://api.daily.dev/og/posts/2dm9cNDmT.png og:image:alt: Issue #633: The life of a ~200ms HTTP request to a Node app — Node Weekly og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Issue #633: The life of a ~200ms HTTP request to a Node app — Node Weekly **[Node Weekly](https://daily.dev/sources/ndwkly)** · 3 min read · 3 upvotes · 1 comments ## Summary Node Weekly issue #633 covers a scroll-driven visualization tracing every step of a ~200ms HTTP POST request through Node's internals and event loop, a proposal to add error codes to the Fetch API spec, a new C-based JavaScript runtime called Ant, a guide migrating from Express to Go's Fiber framework, Vercel deprecating Node 20 on October 1 2026, Playwright CI optimization tips, GitHub security settings for maintainers, Dependabot's new 3-day package cooldown, TC39's upcoming 115th meeting agenda, Cloudflare's new 'Drop' static site deployment tool, and a transpiler converting JavaScript/PHP/Python to PL/pgSQL. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@pdfopsdev** · 0 upvotes > clicked through the whole 200ms viz, curious if it covers connection reuse on the outbound leg. in prod the part that actually eats the budget is usually DNS + a cold TLS handshake to whatever downstream the handler calls, not the event loop itself. keepalive agents fix like half the 'mystery latency' tickets I've ever looked at. ## Similar posts on daily.dev - [Node Weekly Issue 612: February 19, 2026](https://daily.dev/posts/node-weekly-issue-612-february-19-2026-mm7b9kcff) · Node Weekly · 1 upvotes · 0 comments - [Node Weekly Issue 611: February 12, 2026](https://daily.dev/posts/node-weekly-issue-611-february-12-2026-vobr34fos) · Node Weekly · 7 upvotes · 0 comments - [Node Weekly Issue 624: May 14, 2026](https://daily.dev/posts/node-weekly-issue-624-may-14-2026-gtg587gyk) · Node Weekly · 9 upvotes · 0 comments - [Issue \#640: Node is getting a built-in benchmark runner — Node Weekly](https://daily.dev/posts/issue-640-node-is-getting-a-built-in-benchmark-runner-node-weekly-lbgea6xbi) · Node Weekly · 1 upvotes · 0 comments - [Node Weekly Issue 618: April 2, 2026](https://daily.dev/posts/node-weekly-issue-618-april-2-2026-7bwxqpeg8) · Node Weekly · 4 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#nodejs](https://daily.dev/tags/nodejs), [#typescript](https://daily.dev/tags/typescript) [View this post on daily.dev](https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Issue #633: The life of a ~200ms HTTP request to a Node app — Node Weekly","url":"https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt"},"datePublished":"2026-07-16T12:38:39.538Z","dateModified":"2026-07-16T12:38:59.508Z","description":"Node Weekly issue #633 covers a scroll-driven visualization tracing every step of a ~200ms HTTP POST request through Node's internals and event loop, a...","image":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","thumbnailUrl":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","isAccessibleForFree":true,"articleSection":"Node Weekly","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Node Weekly","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/d9a53a9e9f1147e9ba5a36452cc68fad","url":"https://daily.dev/sources/ndwkly"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"javascript,nodejs,typescript","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Node Weekly","item":"https://daily.dev/sources/ndwkly"},{"@type":"ListItem","position":3,"name":"Issue #633: The life of a ~200ms HTTP request to a Node app — Node Weekly"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/issue-633-the-life-of-a-200ms-http-request-to-a-node-app-node-weekly-2dm9cndmt","comment":[{"@type":"Comment","text":"clicked through the whole 200ms viz, curious if it covers connection reuse on the outbound leg. in prod the part that actually eats the budget is usually DNS + a cold TLS handshake to whatever downstream the handler calls, not the event loop itself. keepalive agents fix like half the ‘mystery latency’ tickets I’ve ever looked at.","datePublished":"2026-07-17T18:07:59.415Z","url":"https://daily.dev/posts/2dm9cNDmT#c-YLXx8Fmqm","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]} ```