Database is for shared state, so worker can share state for other workers?
Database is for shared state, so worker can share state for other workers?
Cor not being used that way.
Dwe use Backblaze B2 (could be R2 if you prefer) for this specific dataset; we kinda use it like a key/value store.
There's Cloudflare D1 too that we do use in some of our other Workers
There's Cloudflare D1 too that we do use in some of our other Workers
CAh that's your store eh?
Dit just really depends on what you're trying to do and what's the easiest/best choice for your specific task/situation.
CIs that acid compliant?
Dacid compliant?
CI mean if you got 20 write requests, a read cannot occur till writes are done
Call sorts.
DNo; we designed it so concurrency isn't really a concern.
CEverything is absolutely the state it should be
COh good stuff that is a smack for me at this point.
Dthis doesn't include server maintenance / sysadmin hours though.
CConcurrent requests all coming in and states getting somewhat confused so having to queue requests properly and all sorts is the battle.
Dyou can use Durable Objects if you need a global lock.
CSo what's your product link? Sounds cool ai.moda?
CI'll look into that, have you used them yet?
CI know WebSockets are really fast but their stateful objective makes them kind of BS to work with when scaling you can only say handle "regions" and not all users.
Dnot too much public yet. Fair amount of internal tools that we use for consulting work.
CServer gets overwhelmed and you need to split people off, it's a great but horrible protocol 
DDurable Objects kinda fix that.
CI'll give this a read I haven't seen it though
CWhat's this under?
CI'm a free account not sure I've seen this one.
DWe don't have any Workers using Durable Objects, though I've been planning on learning them properly for months now 
CIs this part of a pro plan+?
Dyou need a paid Worker plan. It's $5/m.
CI kind of want to learn them to be honest, I am in the midst of re-writing my sitee and backend to be more fast this could maybe solve some broker issues if it's dope.
CIt's part of the worker?
DYes.
CThey got free plans if I only test it a few times?
CI'm not even sure about all this new stuff you feel, I'm old-school write it up from scratch and just host more servers and IPC them right.
Ddoing that is a lot of work imo. Once you get the hang of Workers, it's much easier.
CThat may be a solid solution though cause I worry about a single broker keeping say many media servers state of how many weights left, or user slots and if this can make it so I can run many core brokers
Ckeeping it stateful and savage ouuf.
DWorkers can be used on the free plan, just not Workers Durable Objects
CDave I'm the type of guy who can't trust other code, if I write it and bullet-proof it, I know I'm safe and can laugh.
CBut dang, what plan is that for then?
CI was considering PRO for the firewall improvements
DCloudflare scales Workers almost infinitely for many customers.
CYeah I saw I just don't get how it can for a stateful system, that's amazing.
CSo you work ai.moda?
Dthe nice thing is many things don't have to be that stateful when you think about it.
CFor me, it's mostly who is in a room, who is on what media server, the usage of those media servers and calculating where one should go
Cso a single broker for me has a limit of say 100 media servers, 20K users and a broker is a single core.
CI must keep certain track to ensure messages from one user makes it to an entire room or a specific user's inbox while in session.
CBroker must assign chat servers to users/rooms. it's a lot of state checks.
Dimo the Pro plan ($240/year) + Workers paid plan ($5/m) is the best bang for buck.
DDurable Objects using WebSockets is definitely what you want.
CI'm considering it, I just have a grand time with the given firewall and my ability to scout bad ASNs free has worked best.
