The latest articles on DEV Community by Fluxychat SDK (@fluxychat_sdk_330378fbf56). https://dev.to/fluxychat_sdk_330378fbf56 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3946179%2F1fa09408-bc4f-420b-9a79-87d585ffd837.png https://dev.to/fluxychat_sdk_330378fbf56 en Fluxychat SDK Fri, 22 May 2026 13:31:29 +0000 https://dev.to/fluxychat_sdk_330378fbf56/one-durable-object-per-chat-room-what-we-learned-shipping-fluxychat-on-cloudflare-4nho https://dev.to/fluxychat_sdk_330378fbf56/one-durable-object-per-chat-room-what-we-learned-shipping-fluxychat-on-cloudflare-4nho <p>I built FluxyChat (MIT) because I wanted inspectable edge chat without a socket fleet. <br> Hot path: WebSocket → Room Durable Object (ordering + fan-out) → async persist to D1. Cross-room features stay in D1/HTTP.</p> <p>Repo: <a href="https://github.com/AlessandroFare/fluxychat" rel="noopener noreferrer">https://github.com/AlessandroFare/fluxychat</a><br> Beta: <a href="https://www.fluxychat.com/get-started" rel="noopener noreferrer">https://www.fluxychat.com/get-started</a></p> <p>Open questions:</p> <ul> <li>DO hibernation + reconnect storms — what worked for you?</li> <li>Batching D1 writes after broadcast — tradeoffs?</li> </ul> architecture discuss serverless showdev