Cloudflare

they already have: https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/

oh bruh, didn't notice that there was a `cloudflare:sockets` package XD

so i can use mongodb atlas over tcp from workers?

Would probably be a pain to get working because im not aware of any lib that uses cloudflare sockets for it but yes you can

<@905865275583365161> wait... is this closed beta?

No, "The TCP Socket API is available today to everyone."

there's already a mongodb client for deno, i'm trying to port it over and probably post it in <#783765338692386886> later

the design decision with importing it from `cloudflare:sockets` is a bit questionable

a global variable would've been probably the better choice

I think its like that because theres no standard for TCP sockets yet

I can't imagine it would be efficient to ship it with every single deployment ever, if it's never used

you could still analyze the code to check whether the global variable is used

of course, but an import would imo be the more "proper" way :D

if there's no type support - as it looks like - it's pretty stupid

it's also annoying if you use deno for development tbh

if there was a global variable, e.g. `Cloudflare`, you could just add the type to the `workers-types` package

i'm not saying that this feature is bad - it was actually the one feature i waited for all along - but i just don't like its implementation plus i hope that some mongodb client out there will adopt it soon

I'm sure they'll come with a lib type declaration soon enough

indeed, the next release of workers-types will already contain the types for `cloudflare:sockets`, PR is already merged, so just keep an eye on npm/github!

The import was used explicitly to demonstrate that this is a platform-locked API, and not something that is cross-compatible with other runtimes. If/when a standard develops, I assume they would add support for it as a global

i mean if you look at e.g. deno, they use the global `Deno` variable for such features

Guess it is just a platform-based choice then?

is there any known mongodb client out there which supports it already?

Analyzing code is hard, and just adds complexity for something that's not really needed (i.e. the import works).

Also the way the runtime (`workerd`) works, the more global things that are added at runtime the longer the startup time for customers that don't use them - that's why bindings are now available through a variable instead of the global scope.

This says traffic goes by a page rule before getting to a worker
https://cdn.discordapp.com/attachments/779390076219686943/1108443746984542298/image.png

so why a cache hit by a page rule generates a billed worker request ?

i.e if i page the results of a worker with a page rule, and the next requests are a cache hit will i pay for a request to the worker again? or i'm understanding it wrong ?