Cloudflare Workers integration is now possible

Rishi_uttam · 2024-12-09T13:08:06.669Z

don’t think its possible to force developers, plus it does seem like a infrastructure issue as cloud flare workers isn’t a runtime like Node, its a worker thread, similar to the one in the browser.

alexbevi · 2024-12-13T14:40:25.296Z

Hey @A_B7,

We can’t force Cloudflare to do anything, but based on mongodb · cloudflare/workerd · Discussion #2721 · GitHub it sounds like there might be some movement on this in January.

More information will be shared as it becomes available, but I’d recommend following that discussion thread as well for the time being.

James_C2 · 2024-12-16T06:00:40.163Z

HELLO EVERYBODY! I got it to work!

I was able to get the mongodb driver to work in cloudflare workers using module-aliases and TCP sockets!

Its a very minimal implementation and I would really be very grateful for any contributions to the repository

I was able to achieve this by using module-aliases to polyfill the net.createConnection and tls.connect functions and make it return a mock Socket that utilizes cloudflares TCP sockets

The repository can be found here

BlindChicken · 2024-12-17T03:16:20.004Z

James you are the BEST! I just tried it out and it appears to work. I only tried on a single call to the database but it worked. I’m using it within a React-Router7 app deployed on workers.

There remains one small issue, not with the polyfill, but with the workers/mongodb Atlas integration. The problem is that network access to your cluster is only possible via IPv4, and CF-workers all use the the same IPv6 address, specifically 2a06:98c0:3600::103. As I see it, one needs to allow open access to the cluster, which really isn’t great for security.

A_B7 · 2024-12-17T03:16:33.151Z

npm error 404 Not Found - GET https://registry.npmjs.org/cf-mongodb-polyfills - Not found

Going to download it right now and manually try it

A_B7 · 2024-12-17T03:16:35.086Z

GitHub

mongodb · cloudflare/workerd · Discussion #2721

The mongodb does not work even with node_compat_v2 on. It can be imported, but it does not properly connect to a DB. The package relies on net.Socket and tls.TLSSocket. See Issue for more context: ...

…or can you…

BlindChicken · 2024-12-17T14:52:25.162Z

Not sure why, but the link in James’ post is now dead. But here are the links:
Repo: https://github.com/jchoi2x/cf-mongodb-polyfills
NPM(github): Package cf-tcp-mock · GitHub
And there seems to be an issue Github, pages are really slow to load.

Imtiaj_Bin_Aoual · 2024-12-28T13:28:10.904Z

it seems to be working. but getting some weird cross promise resolution issues connecting and disconnecting db in the index.ts
any suggestion on how to handle connection and disconnection?

A_B7 · 2025-01-14T22:34:00.539Z

github.com/cloudflare/workerd

add node:net module

cloudflare:main ← cloudflare:yagiz/add-node-net

opened 10:12PM - 09 Jan 25 UTC

anonrig

+2768 -21

> Work in progress. Based on @jasnell's pull-request https://github.com/cloudfla…re/workerd/pull/2217 with couple of changes/additions ### TODO - [x] Write a bazel rule for testing TCP servers through Node.js - [x] Add tests

what’s my reward?

Ben_Kennedy · 2025-01-15T18:19:02.981Z

I am unable to get GitHub - jchoi2x/cf-mongodb-polyfills: Allows using of mongodb npm package in cloudflare workers environment by polyfilling missing modules working with Atlas. I wonder if it’s because of the IPv6 address access problems between cloudflare & Atlas. Not sure how to fix that. Opened an issue here: BSONOffsetError error when trying to load from Atlas · Issue #4 · jchoi2x/cf-mongodb-polyfills · GitHub

A_B7 · 2025-01-15T19:22:02.451Z

github.com/cloudflare/workerd

add node:net module

cloudflare:main ← cloudflare:yagiz/add-node-net

opened 10:12PM - 09 Jan 25 UTC

anonrig

+2768 -21

> Work in progress. Based on @jasnell's pull-request https://github.com/cloudfla…re/workerd/pull/2217 with couple of changes/additions ### TODO - [x] Write a bazel rule for testing TCP servers through Node.js - [x] Add tests

you dont need that anymore.

Rishi_uttam · 2025-01-16T00:03:50.884Z

Awesome, is this/can this be an official release that workers now support Mongodb drivers? The community solve the data api deprecation!

alexbevi · 2025-01-16T02:25:56.684Z

It is very exciting that Cloudflare is making progress on this. I haven’t had a chance to test these changes yet, but given this is just adding support for node:net, to connect to Atlas they’ll likely still need to implement node:tls.

BlindChicken · 2025-01-21T02:00:42.421Z

Hello Ben,
I am also getting the same error BSONOffsetError but I am only getting it intermittently. I am certain that it is not related to the polyfill. As far as I can tell, it is likely due to a memory limit, or some other limit. I’m getting the error on M0 free cluster, when doing $vectorSearch. I can prevent it from occurring by setting a low limit, eg: 1 or 2 docs, as opposed to 10 or more. I don’t see any errors in my MongoAtlas dashboard, nor do any appear in Cloudflare.

If I run my app in locally in dev mode (not using wrangler) I don’t get the error, but with Wrangler, in preview or deployed, I do get the errors. So not really sure what is causing the issue, but it is frustrating.

I should probably file an issue, but I’m not sure where, any suggestion?

alexbevi · 2025-03-25T18:12:24.586Z

Just wanted to close the loop with an update blog post: Cloudflare Workers and MongoDB | ALEX BEVILACQUA

The latest release of Cloudflare Workers should support connectivity and interaction with MongoDB Atlas. I haven’t done a full barrage of testing, but I can confirm the limited tests I ran are successful

Arnaud_JEZEQUEL · 2025-03-26T16:00:24.379Z

Thank for the test. Unfortunately i’m still getting a
“MongoServerSelectionError: socket.once is not a function”

A_B7 · 2025-03-26T16:29:18.131Z

because @alexbevi is, according to his own blog post, fully responsible for this fix release, you should hold him accountable for any issues

alexbevi · 2025-03-26T20:43:47.076Z

pretty sure that’s not what I’m implying (though I might have made the most noise) … but based on the error it does’t seem the workerd was updated to pull in the latest dependencies.

Arnaud_JEZEQUEL · 2025-03-31T15:38:01.640Z

Maybe, though i followed your nice blog post

wrangler.toml

compatibility_flags = [“nodejs_compat_v2”]
compatibility_date = “2025-03-20”
pages_build_output_dir = “.svelte-kit/cloudflare”

I will have a look again i might have missed something (for now i’m staying on Vercel)

tae2_N_A · 2025-04-06T09:48:22.508Z

same here! I’m still getting a “MongoServerSelectionError: socket.once is not a function” in sveltekit project