Setting the file. One moment.
Subchapter 6.1
references/rules.mdMarkdown3 KBView on GitHub
Choose one object per entity that needs coordinated state. Keep essential data in durable storage; in-memory state must be reconstructible. Prefer SQLite for new classes, and inspect the backend of existing classes before selecting APIs. For idle WebSocket servers, prefer hibernation and plan for state restoration.
Fetch the relevant current documentation before implementing or reviewing changes.
For verification, use Testing Durable Objects. Keep API signatures, configuration, limits, and implementation examples in the linked docs.