---
type: "post"
id: "serverless-routing-made-sticky-analysis-5547c6"
slug: "serverless-routing-made-sticky-analysis-5547c6"
title: "Serverless routing made sticky"
description: "**Thesis:** Sticky Sessions move serverless routing from independent requests toward session-scoped continuity, making session lifecycle and capacity the operational unit for stateful workloads."
retrieval_nugget: "**Thesis:** Sticky Sessions move serverless routing from independent requests toward session-scoped continuity, making session lifecycle and capacity the operational unit for stateful workloads."
published_at: "2026-10-21"
updated_at: "2026-10-21"
record_date: "2026-10-21"
date_kind: "published_at"
topics: ["infrastructure"]
source_urls: ["https://modal.com/blog/serverless-routing-made-sticky"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:serverless-routing-made-sticky-analysis-5547c6"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:a7af161c51951e3124ad2e36e4d5137265c4560dd73789445ad35ef114dc2cb4","reviewed_at":"2026-10-21T00:01:46.511Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Sticky Sessions move serverless routing from independent requests toward session-scoped continuity, making session lifecycle and capacity the operational unit for stateful workloads.","observed_facts":[{"text":"Modal says every request in a session is routed to the same container and session tokens encode routing metadata validated by its proxies.","source_urls":["https://modal.com/blog/serverless-routing-made-sticky"]},{"text":"The post says autoscaling monitors active session counts and queued demand; containers can be configured for one or more concurrent sessions.","source_urls":["https://modal.com/blog/serverless-routing-made-sticky"]}],"mechanism":"Token-carried routing metadata identifies the session's container; the owning host tracks lifecycle, while load balancers use periodically probed concurrency snapshots and recent routing decisions.","why_now":"Modal identifies voice agents, streaming speech-to-text, stateful web UIs, and multiplayer games as workloads where reconnecting to a different process can lose continuity.","implications":["Builders gain a managed routing primitive for stateful interactive workloads, while session concurrency and queueing become explicit capacity concerns.","Session affinity alone does not establish durable application state or recovery after container loss."],"evidence_boundary":"The evidence is Modal’s product engineering post; it describes the design and intended use cases but provides no independent benchmark or reliability results.","watch_conditions":["Watch for published behavior under container replacement, session expiry, and overload, including whether active sessions recover or fail and how queue delays vary with session concurrency."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied, so this release starts a distinct record about session-scoped serverless routing and its operational model."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/serverless-routing-made-sticky-analysis-5547c6/","markdown":"https://newruntime.com/posts/serverless-routing-made-sticky-analysis-5547c6.md","json":"https://newruntime.com/posts/serverless-routing-made-sticky-analysis-5547c6.json"}
---

# Serverless routing made sticky

## Retrieval answer

**Thesis:** Sticky Sessions move serverless routing from independent requests toward session-scoped continuity, making session lifecycle and capacity the operational unit for stateful workloads.

**Thesis:** Sticky Sessions move serverless routing from independent requests toward session-scoped continuity, making session lifecycle and capacity the operational unit for stateful workloads.

**Observed facts:** Modal says every request in a session is routed to the same container, and that session tokens encode routing metadata validated by its proxies. The post also says autoscaling monitors active session counts and queued demand; containers can be configured for one or more concurrent sessions.

**Mechanism:** Token-carried routing metadata identifies the session's container; the owning host tracks lifecycle, while load balancers use periodically probed concurrency snapshots and recent routing decisions. This design keeps the routing map out of proxy state while retaining an affinity target tied to a session.

**Why now:** Modal identifies voice agents, streaming speech-to-text, stateful web UIs, and multiplayer games as workloads where reconnecting to a different process can lose continuity. Session affinity addresses that gap without the scale ceiling of setting max_containers=1.

**Implications:** Builders gain a managed routing primitive for stateful interactive workloads, while session concurrency and queueing become explicit capacity concerns. It does not by itself establish durable application state or recovery if a container disappears. **Evidence boundary:** The evidence is Modal’s product engineering post; it describes the design and intended use cases but provides no independent benchmark or reliability results.

**Watch condition:** Watch for published behavior under container replacement, session expiry, and overload, including whether active sessions recover or fail and how queue delays vary with session concurrency.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Infrastructure](https://newruntime.com/topics/infrastructure.md): Explore the infrastructure topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)