Shados
CDCloudflare Developers
•Created by AJR on 2/11/2025 in #hyperdrive
Yes, that is correct. We've kicked
Our frontend and backend-for-frontend are in workers, but the database connections are made from a .NET service living in Azure for historical reasons and in-house investments on that tech stack, thus why the db connection isn't made from the worker)
3 replies
CDCloudflare Developers
•Created by AJR on 2/11/2025 in #hyperdrive
Yes, that is correct. We've kicked
especially if it ends up exposed as just a passthrough to Postgres (so I could connect to it using regular drivers with no change to my app aside for the connection string)
3 replies
CDCloudflare Developers
•Created by AJR on 2/11/2025 in #hyperdrive
Yes, that is correct. We've kicked
Pretty simple use case. We have a database that is currently in US East, but gets consumed from the west coast, Europe, and SE Asia.
Right now now we're using read replicas to reduce latency between the regions, with all the costs and complexity that comes with it. Lowering latency even a little could remove the need for some of these replicas (at least West Coast and Europe), and query caching could improve performance even further. We have an enterprise Cloudflare plan, so the whole "No additional extra costs" for Hyperdrive would be a great value add for "free" for us.
3 replies
CDCloudflare Developers
•Created by AI on 1/21/2025 in #workers-help
browser rendering api pricing
AFAIK its part of your worker plan, and doesn't incure additional costs, just need to be within the limits (it fails if you don't, so no risk).
3 replies
CDCloudflare Developers
•Created by Shados on 11/12/2024 in #workers-observability
Hi all, can someone confirm to me if
thank you!
4 replies
CDCloudflare Developers
•Created by Shados on 9/17/2024 in #pages-help
Exceptions not being logged
Ok, searching through this discord and doing more tests, it looks like I had some misunderstanding of how this works. Remix was handling the exception (I thought i was throwing it outside of the Remix context, I was wrong), and returning a 500 which is not an "exception" in Cloudflare. If I use the Remix global server error handler in entry.server.tsx and manually logs an exception there, it shows up (as a log). There's no real way to log an actual exception since Remix handles all of them.
One caveat I haven't found a good solution for, is if there's an exception from the getLoadContext callback. That one doesn't get handled by the server handler, but still ends in a 500.
So it seems you REALLY want a try/catch around your getLoadContext to get any kind of error reporting from there.
2 replies