One sec

So Lets say I have

class Comments {
  
}

class Posts {
   constructor(...args) {
    super(...args)
    this.comments = []
  }
}

class Users {
  constructor(...args) {
    super(...args)
    this.posts = []
  }
}

Now on this if I want to do use cases like, 1. Search by post names 2. Search/filter by users 3. Search/filter posts by dates

Basically, the example I have added in https://github.com/subhendukundu/worker-auth-providers Looking a bit boring. So I was thinking to add a more realistic example 😄

Hmm, I honestly wouldn't use Durable Objects for that - a database with PostgREST would most likely be the better option.

For sure! I was thinking in terms of capabilities.

There's

Array.find()

and

Array.filter()

if you need to search through an array, but it is not an option for a million records.

in real life, what colud be a max number? If you have an idea, would love to know.

However many records you can search through in 500 ms 😛

haha 😄

I was just putting a test case

to see how many I can filter

while you gave me that answer

But thank you so much 🙂 it helped.

Yeah I'd store posts and users in a db, and then query for them. However, you could technically have one DO per user and post, where the db would hold the key/id to it.

But I'm unsure what benefit it would give over just storing it in a db, unless you're thinking about some real-time actions with websockets

Yes, real-time actions with websockets That is the use case.

Basically just trying to put together a fun example with DO and workers WS.

Yeah same story here! In my case I'm creating a protoype of online pictionary, creating DO for the lobby and for each room. Still working on the frontend part, but can't wait to see how DO will perform 🙂

Previously I just hosted a monolith on my computer, and since then I've been waiting for the serverless way to create fun simple online games. I think... DO + WS is the answer!

Ya, This is great use case. I have quite a few usecases in mind. Just to play around basically

I think in your case, you could have DO per post, showing how many users are reading the post, some real-time interactions, etc! 🙂

Having one large DO for all posts wouldn't really scale

I must say I'm a little surprised how little attention DO is getting, based on it's capability and power. Perhaps a few blogs and real-time demos would do the trick for it to get more attention. When I first heard about DO, I wasn't too sure how it worked or how I could utilize it for my use cases. I only read over the doom blog, and I believe it was too technical and the doom network code was just too much! 🙂

Exactly! I am sure @User and team definitely working on that. 🙂 But ya, it would be fun use case I am trying to put together if I am able to pull it off.

Yeah, can't wait to see more experiments with DO + WS 🙂

100%

hmm! there are two ways to go about this. 1. One DO, for User which has all of his posts. 2. One DO for each Posts

Seems 2nd one is better approach.

The second option would scale better, since each DO has its limits (can't scale vertically)

The User DO could fetch the Post DO that the user is reading. But I'm not too sure if an user DO is really needed. In my case I will have a GameRoom DO, where each user connected to it will have basic metadata such as UserId, username, etc. If I need more information about the user I could juse fetch his information from KV (or any other DB)