There's nothing native to the Workers platform, but they do have a partnership with mailchannels to let you send out email for free, you don't need a mailchannels acct

ok

Is there any performance difference between the wokers-rs version and typescript one?

Unless it’s something WASM/Rust excels at it’s on par

For a “Hello World” it’d probably be slower

Thought so but just wanted to make sure

How you guys manage

waitUntil

in code ? I have lots of

waitUtil

calls in lots of functions so that I can respond quicker, but they are messing up my code.

I don’t personally have any issue with having them here & there as necessary - is it just the readability you’re concerned with?

Yes it is readability

Hmm and parameter passing. I have to pass the context all around to use that waitUntil

If I want to schedule a POST request to happen in like 12 hours, what should I use?

Aren’t Durable Objects only good for up to 30 seconds?

You can use DO Alarms and use setAlarm

for anywhere in the future

For context, I’m trying to allow my mail API to schedule email sends in the future.

Like even a week in the future?

yes

ive used it for months into the future as well

they dont incur duration costs either

Huh interesting, so just storage costs?

- Regular duration costs only during execution but not while waiting 1 week, or 1 year - Your mail API would write once to storage and once to set the alarm, then an extra request when the time comes to invoke the alarm & another to read storage - The alarm gets deleted once ran but you would need to manually delete the storage for whatever mail you have stored

It was a little unclear when I was reading through the docs a while back so thought I'd share

alarms also retry automatically in different places if one location fails which is really cool

I come with another question about the appropriate tech to use for something I plan on building. Currently I'm building workers for an API that is using Planetscale as a DB, as well as slightly using KV for some smaller purpose. I'm going to be adding a worker that collects data from an API and caches it, then will fetch from that cached version for requests to the API. (For context, the data is leaderboard data that'll be updated every ~2-3ish minutes or so. But I don't want to make a request to the API every time) Any recommendations for how to handle this most cost effectively? Would it make sense to throw the leaderboard data in KV? Or just put it in my database? The leaderboard data will include multiple seasons, only the latest season actually having any changes.

or can I use the Cloudflare cache system somehow for this 🤔

LOL I just asked ChatGPT and it gave me a solid answer

You literally have a "Cache API" for free (of money)

hey friends - is there any downside/performance ramifications (even just short-term hiccups) to switching to "workers unbound" pricing instead of the standard workers bundle?

did some quick maffs and it seems a bit cheaper for our use case. wondering if there's any possible reason not to switch

It'll be cheaper whenever you get at least 10 million requests per month, and your average request processing time is <225 milliseconds