Durable Object WebSocket Hibernation

A two-part series on what WebSocket hibernation actually changes in Durable Object architecture. First: the runtime mental model. Second: why the billing impact can be dramatic for long-lived but mostly idle real-time systems.

1 Mental Model

What hibernation changes in the relationship between the WebSocket connection and the Durable Object's active compute lifetime.

2 Cost Model

Why hibernation can reduce duration charges dramatically when connections stay open but messages are infrequent.

Read The Series

Mental Model
Cost Model

The Through-Line

without hibernation:
connected socket keeps DO awake

with hibernation:
socket stays connected
DO can sleep between events

That separation between connection lifetime and compute lifetime is the whole story.

Memory Line

WebSocket hibernation is not about closing the connection. It is about letting the Durable Object stop paying active-compute rent while the connection remains accepted.

2-part series