durable-objects-pattern-checker

Detect improper Durable Object patterns by validating ID generation methods (idFromName, newUniqueId), state persistence, hibernation implementation, and lifecycle handling. This pattern checker enforces correct stub usage and prevents anti-patterns that compromise consistency and performance.

Common mistakes include inconsistent ID reuse, improper hibernation configuration, missing persistent state storage, and incorrect lifecycle initialization. This checker identifies these issues to ensure strong consistency and prevent data loss or duplicate instance creation.

Use idFromName for deterministic, reusable IDs when state must persist across requests, and newUniqueId for one-time instances. Correct ID patterns ensure DO instances are properly reused and state remains consistent, avoiding unintended instance duplication.

Hibernation requires correct alarm scheduling, proper request handling during hibernation, and state preservation across lifecycle events. Proper implementation reduces memory overhead while maintaining strong consistency and preventing state corruption.

Yes, Durable Objects support real-time interactions via WebSockets with proper lifecycle and state management patterns. Correct implementation ensures messages persist, connections resume reliably, and state remains strongly consistent across reconnections.

State persistence failures typically stem from incorrect ID patterns, missing durable storage calls, or improper initialization. This checker validates state management patterns to ensure data survives instance hibernation and request cycles.