/

Tutorials How-to guides Explanation Reference About

Reference

Components Eras Research tree

Stripe Billing DNS round robin Load balancing Health checks Managed identity Caching Connection pooling Read replicas Eager loading Query analysis Structured logs Metrics Percentiles Alerting Funnel analytics PHP-FPM OPcache Ruby Node.js Python Node.js cluster mode libuv thread pool Laravel Rails Express Django Symfony Sinatra Flask Connection reuse Compression Timeouts and retries Load balancing algorithms Continuous delivery Code review Automated tests Full-text search Object storage Content delivery Web application firewall Background jobs Message queues Stampede protection Cache warming Go Java C#Gin Spring Boot ASP.NET Core Distributed tracing Trace search Notebooks Certificate automation Elixir Rust Zig Haskell Phoenix Checkout Tiered caching Multiple zones Autoscaling Container orchestration SLO dashboards Error budgets Backoff with jitter Circuit breakers Priority load shedding Idempotency keys Read-your-writes routing Go GC tuning Axum Actix Web ZGC Data warehousing Hosted models Model serving Point-in-time recovery TLS everywhere HTTP/2 Synchronous replication Restore drills Dependency scanning Sharding Encryption at rest Multiple regions GeoDNS Infrastructure as code GitOps Anycast HTTP/3 Notifications Hybrid fan-out Leaderless replication Consensus databases Disaster recovery drills SOC 2 program Data residency controls Security team Investor relations Guidance modeling

Runtimes and frameworks Incidents Glossary Team and work Instances and regions Exits and Legacy Sandboxes

ReferenceResearch tree

Era 5 · Series C

HTTP/3

20% off the user hop to distant users.

Prerequisites#

Research these first: HTTP/2.

Engineering terms#

HTTP/2 and HTTP/3

HTTP/3

Track: Performance
Era: Series C
Cost
Requires: HTTP/2

See also

Research treeEvery Research item by track and Era: what it costs in Insight, what it needs first, and what it unlocks.

Game version 17

On this page

Prerequisites
Engineering terms