RPC hasnt even been out for a month yet "soon" in cf talk generally means at least a few months
RPC hasnt even been out for a month yet "soon" in cf talk generally means at least a few months
UAnd fwiw worker requests are only 30 cents for a million requests even doing like 10 rpc calls is still a crazy good deal
Lreferring to this post. didn't quite make it this weak doesn't sound like months https://twitter.com/irvinebroque/status/1776331933129253290
@sperand_io @elithrar @Cloudflare Two things here:
- We are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request. (so that pricing doesn't disincentivize breaking apart an app into many Workers) Coming soon.
4/5/24, 7:31 PM
UI’m aware of the post but still it will probably be a few months for that to be added
KIf you don't read the response body then it will show as cancelled
Npossible to export a whole kv ?
Nfound a way, you cna use the wrangler cli and just redirct the output to a file
HService Bindings don’t pass through the Cache Layer, so you need to invoke the Cache API manually
HIIRC Smart Placement is only used if the first Worker invoked is SmartPlaced
HNot sure then, sorry
JIs there any way to get a longer execution time in a worker than 1 min if it is triggered by cron every 5-10 min?
JI'm seeing this error crop up from time to time:
The destination execution context for this RPC was canceled while the call was still running.
The destination execution context for this RPC was canceled while the call was still running.
SDoes anyone manage to build an email validator with cloudflare workers? to verify whether the email exists or not
MHey guys i am coming back to cloudflare workers after falling down the rabbit hole of nest js server development although really fun and cool, I feel that cloudflare workers was so easy to get going fast. As we stand today can i jump in cloudflare tools like workers, durable objects, and queues to develop a pretty capable platform backend api for something like a ecommerce website with hundreds of thousands of orders per day
UWorkers can do a lot, and would easily be able to handle the traffic you would need.
MIs queues good as it is today to handle event driven microservices
UQueues is decent there have been some issues I have seen pop up with regards to concurrency, biggest concern there is the fact that it is not GA
MI built a mvp on cloudflare workers and when i got to queues i got overwhelmed. I used upstash queues tho i found alot of failed events/messages it made me overwhelmed with not being able to figure out
MWhat set of tools does cloudflare present to build a full backend as I would with for example a nest js server.
UObservability is cloudflare's biggest downfall. They did recently acquire baselime which is a pretty good tool so hopefully it gets better.
MOkay so would you choose cloudflare workers or falling down the nest js path
UMost people here use https://hono.dev as their framework but its more express-like than nest. Not sure if nest would work on workers or if there is a good alternative close to it.
Hono is a small, simple, and ultrafast web framework for the Edges. It works on Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, AWS Lambda, Lambda@Edge, and Node.js. Fast, but not only fast.
MI find nest js and spring boot just sooo capable in terms of building backends.
MI meant using nestjs on something like GCP cloud run
MI am one developer I love to code so much i do it 19 hours a day unhealthy lol. I am trying to build mvp backends that can handle a good amount of users.
MI want to do it fast, spending way more time in learning to build backends then actually building thme
UI mean if you already know and use nestjs on GCP cloud run you should probably just stick to that
MI built an mvp with hono and cloudflare workers. I loved them
MI just went away from that way of building backends because nest promised the whole domain driven design, hexagonal architecture, etc
