| title | Durable Object Base Class | ||
|---|---|---|---|
| pcx_content_type | concept | ||
| sidebar |
|
import { Render, Tabs, TabItem, GlossaryTooltip, Type, MetaInfo, TypeScriptExample, } from "~/components";
The DurableObject base class is an abstract class which all Durable Objects inherit from. This base class provides a set of optional methods, frequently referred to as handler methods, which can respond to events, for example a webSocketMessage when using the WebSocket Hibernation API. To provide a concrete example, here is a Durable Object MyDurableObject which extends DurableObject and implements the fetch handler to return "Hello, World!" to the calling Worker.
async fetch(request: Request) {
return new Response("Hello, World!");
}
}
</TypeScriptExample>
<TabItem label="Python" icon="seti:python">
```python
from workers import DurableObject, Response
class MyDurableObject(DurableObject):
def __init__(self, ctx, env):
super().__init__(ctx, env)
async def fetch(self, request):
return Response("Hello, World!")
fetch(request ): | - Takes an HTTP Request and returns an HTTP Response. This method allows the Durable Object to emulate an HTTP server where a Worker with a binding to that object is the client. - This method can beasync.- Durable Objects support RPC calls as of compatibility date 2024-04-03. RPC methods are preferred over
fetch()when your application does not follow HTTP request/response flow.
- Durable Objects support RPC calls as of compatibility date 2024-04-03. RPC methods are preferred over
request- the incoming HTTP request object.
- A or .
alarm(alarmInfo? ): |- Called by the system when a scheduled alarm time is reached.
- The
alarm()handler has guaranteed at-least-once execution and will be retried upon failure using exponential backoff, starting at two second delays for up to six retries. Retries will be performed if the method fails with an uncaught exception. - This method can be
async. - Refer to Alarms for more information.
alarmInfo(optional) - an object containing retry information:retryCount- the number of times this alarm event has been retried.isRetry-trueif this alarm event is a retry,falseotherwise.
- None.
webSocketMessage(ws , message ): | - Called by the system when an accepted WebSocket receives a message. - This method is not called for WebSocket control frames. The system will respond to an incoming WebSocket protocol ping automatically without interrupting hibernation.- This method can be
async.
- This method can be
ws- the WebSocket that received the message. Use this reference to send responses or access serialized attachments.message- the message data. Text messages arrive asstring, binary messages asArrayBuffer.
- None.
webSocketClose(ws , code , reason , wasClean ): | - Called by the system when a WebSocket connection is closed.- With the
web_socket_auto_reply_to_closecompatibility flag (enabled by default on compatibility dates on or after2026-04-07), the runtime automatically sends a reciprocal Close frame and transitionsreadyStatetoCLOSEDbefore this handler is called. You do not need to callws.close()— but doing so is safe (the call is silently ignored). - On older compatibility dates (before
2026-04-07), you must callws.close(code, reason)inside this handler to complete the WebSocket close handshake. Failing to reciprocate the close will result in1006errors on the client, representing an abnormal closure per the WebSocket specification. - This method can be
async.
- With the
ws- the WebSocket that was closed.code- the WebSocket close code sent by the peer (e.g.,1000for normal closure,1001for going away).reason- a string indicating why the connection was closed. May be empty.wasClean-trueif the connection closed cleanly with a proper closing handshake,falseotherwise.
- None.
webSocketError(ws , error ): | - Called by the system when a non-disconnection error occurs on a WebSocket connection. - This method can beasync.
ws- the WebSocket that encountered an error.error- the error that occurred. May be anErrorobject or another type depending on the error source.
- None.
ctx is a readonly property of type DurableObjectState providing access to storage, WebSocket management, and other instance-specific functionality.
env contains the environment bindings available to this Durable Object, as defined in your Wrangler configuration.
- Use WebSockets for WebSocket handler best practices.
- Alarms API for scheduling future work.
- RPC methods for type-safe method calls.