you could do a single worker and instead of using crons you could use durable object alarms
you could do a single worker and instead of using crons you could use durable object alarms
Sprobably yes
Sthe cache is per colo btw
Sinteresting! so bind a single worker to a DO and put all the scheduling logic there?
Ssort of, but in your case you might want multiple DOs for each cron to simplify the scheduling. although I've also seen a library that would help with this (can't find it...)
Scan make your own scheduler with a single DO (but multiple instances) like this using
itty-durableand the DO can import whatever code it needs to from your codebase directly
S(
itty-durable
DDoes
.fetch on a Service Worker binding do anything with the cache-control header?
LLearn how to create a serverless REST API using Cloudflare workers and MongoDB Atlas.
IThat's Atlas only but yes.
I(Atlas is their hosted service)
DCan I do a Worker service binding from Worker #1 in local mode (
wrangler devwrangler dev --remoteGitHub
The documentation provides a non-existent argument for
pages devseems like no?
Mwould you guys say that cloudflare workers are fully capable of building a hotel PMS system? I have seen alot of people use workers for MVP but wondering if you guys reccomend it for a scalable saas
Sit scales yes
SWeb Scale
Min what cases would you guys say yeah go with monolith because cloudflare workers wont be a good fit for that
UI would personally never go with a monolith 
Utheres serverless cases for probably everything
CI mean depends on the stack. If you need lots of pieces then monolithic can be easier to maintain and deploy
MI guess I’m just wondering what the limitations of cloudflare workers are. Is it recommended to build a whole saas hotel reservation system on it for example
UCan you build a hotel reservation system on workers - yes. Should you? Do you know how to use cloudflare can you hire people who are good at cloudflare.
MYes I’d say I’m good at building apis on workers with honojs. I’m a one man team
Mdoes anyone know how I can make npx wrangler dev use data the is in my deployed worker. It was using it but its now stale for some reason
CLike a binding?
MNo like I have DO persistent storage data in my deployed worker
MI want to basically run npx wrangler dev and use the latest data that is in deployed worker.
MI thought that happened automatically whenever I restart npx wrangler dev but for some reason its not right now.
MI am using the latest version of wrangler btw
CHave you tried using the
--remote
MWhere's the best place to raise small issues with the Workers docs?
KGitHub
Cloudflare’s documentation. Contribute to cloudflare/cloudflare-docs development by creating an account on GitHub.
MThanks @kian 
one other quick question, I see on the community forums it is possible to route a Worker request to a specific colo. But I can't seem to find where this is documented
one other quick question, I see on the community forums it is possible to route a Worker request to a specific colo. But I can't seem to find where this is documentedKIt isn’t documented since it isn’t a feature that’s available
Mok thanks! for context, im trying to build something similar to durable objects I tried DO's but performance was not great from Australia, with each round trip to DO costing 200-400ms. My target roundtrip is 20-30ms
I read that each worker has a singleton in each colo with shared memory, having access to the routing would help me build something do-like. Is that a good enough use case to gain access to custom routing?
I read that each worker has a singleton in each colo with shared memory, having access to the routing would help me build something do-like. Is that a good enough use case to gain access to custom routing?
UI’m not sure they even really offer that to enterprise customers beyond maybe jurisdictions but also using global scope is something suggested not to do
MIt seems to be recommended here:
https://developers.cloudflare.com/workers/platform/limits/#memory
https://developers.cloudflare.com/workers/platform/limits/#memory
Use global variables to persist data between requests on individual nodes
MThere is also a thread about the ability to route to a specific worker DC colo: https://community.cloudflare.com/t/how-to-run-workers-on-specific-datacenter-colos/385851
M
�Is it possible to make auto-deployments only trigger when a pull request is made on a github branch? As opposed to on every single commit?
IIm building out a discord bot which requires a response in 3 seconds. My function will take longer than that so I need to execute a separate worker separately to run my function and update discord when its done. Is it do-able to call another worker and then return/end my current worker?
KYou return a deferred response and use waitUntil to patch that message
KIn Workers, any incoming HTTP requests are referred to as "fetch" events. A Worker will respond to the HTTP request with the handler method that was …
IThanks, the example I am building off of uses itty-router, which I think uses the ES modules format. This article helps, I think I was just missing the context variable. Thanks!
HI would note too that even requests from the same device(and not the same app) can be routed to two different datacenters, so you aren’t guaranteed to ever hit the same one twice
MIn aware - see the community thread I linked to where it’s mentioned that you can route requests to a specific Colo after it hits the first worker
HAs far as I can tell with that specific demo, it will route you to a specific Colo(which may contain multiple datacenters). And even then, you still aren't guaranteed to hit the same physical machine(or isolate, depending on traffic levels), which would be required to be able to reuse the global scope.
Bhello everyone, I am working on streaming text data from an OpenAI endpoint to my client while maintaining the stream's continuous nature. However, I keep encountering an error that suggests the ReadableStream is expected to handle byte-like data. Is there a way to configure TransformStream to work with text or string data instead?
BUncaught (in promise) TypeError: This ReadableStream did not return bytes.