Building Pub-Sub with Durable Objects
Can anyone suggest a potential architecture using Durable Objects in order to create a "BuddyList" functionality? The goal here is to be able to propagate status updates ( online / offline ) at scale to all users belonging to the BuddyList.
Our current design uses a DO instance per user and our
Does that make sense? We've found the fan-out is brittle, timeouts happen, probable issues with fan-out storms. Retries with back-offs aren't great either. We don't really have the luxury of a status update failing.
I think the question is generalized as how could we design a pub-sub using DOs? I'm at a bit of a cross-roads here trying to figure out the best solution. In our previous system ( before CF ), we used a Redis cluster to maintain buddylist state and this solution worked well for buddylists up to 1,000 members in size.
Our current design uses a DO instance per user and our
setStatus()Does that make sense? We've found the fan-out is brittle, timeouts happen, probable issues with fan-out storms. Retries with back-offs aren't great either. We don't really have the luxury of a status update failing.
I think the question is generalized as how could we design a pub-sub using DOs? I'm at a bit of a cross-roads here trying to figure out the best solution. In our previous system ( before CF ), we used a Redis cluster to maintain buddylist state and this solution worked well for buddylists up to 1,000 members in size.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,529Members
Resources
Similar Threads
Was this page helpful?
