I hope you see a discount at those prices per 1,000 requests
I hope you see a discount at those prices per 1,000 requests
Cor are paid properly for it
CThat's brutal, I almost got smoked with some serious bandwidth pricing starting out with my stuff; literally using over several TB a server a day.
Dit's actually $10 per 1000 pages, so worse than that lol.
CYeah I hope you got the costs sorted out that's for damn sure
Chaha
Dwe have <1,000,000 unique pages. iirc we have like 100,000 unique pages indexed maybe?
Cslowly reading this durable objects with websockets
DI think we've used $2k-$3k of Azure credits on OCRing.
CIf it works it works
CMy prices would had been like 10K+ a month for several hundred users at a time.
Dit's faster and easier to just hit the Worker than maintain a database to track what has been OCR'd vs not OCR'd yet.
CFound good hosting it's like $400CAD for it all
CDatabase 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?
