mongodb

[mikenomitch]

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: cloudflare/workers-sdk#6684
See Blog for more context: https://alexbevi.com/blog/2024/09/11/why-cloudflare-workers-dont-work-with-mongodb/

[vicb]

@xofyarg reported an issue on the unenv repo which @pi0 fixed.

It should be integrated in unenv with cloudflare/workers-sdk#6920

[vicb]

/cc @ricky11 @anonrig

[anonrig]

Working on this - #3315

[tobsn]

/cc @ricky11 @anonrig

it's been forever now... I can't remember when I encountered this the first time but it must be at least 2 years ago.
as new mongodb atlas instances now dont even list the deprecated data api menu tab and the existing instances will only be available for one more year, it's about hot damn time this gets fixed... ;)

thanks!

[anonrig]

Working on this - #3315

[tobsn]

Working on this - #3315

thank you! this way we can use cloudflare AI on cloudflare workers and still use our mongodb atlas instance... it will save us a massive amount of time and energy. I assume that will be the same with a lot of other people once they realize the September atlas data API deprecation deadline is approaching ... anyway, thanks again! immensely appreciated!

[faradaytrs]

I saw the thread on the forum which says that the only problem is that workers don't support TLS

[Yusaney]

I've started a new Mongodb instance, and I can't use it with my Cloudflare workers; I want to use a Cloudflare environment with queues, kv, etc., but I can't use it if workers don't actually work...

[tobsn]

/cc @ricky11 @anonrig

December 6th

[ricky11]

Amazing, tls support for workers whereby native mongodb drivers would work! that would be such a blessing!

[alexbevi]

@anonrig this is great news!

[Imtiajrex]

any movement on this @anonrig

[anonrig]

I've opened an in progress PR - #3315

[anonrig]

TLSSocket and connect() has landed into main. It will be available to the general public in the next couple of weeks.

[DaryeDev]

How can one use mongodb on Workers, now that node:net is merged?

[DaryeDev]

Great to know, thanks!

[vicb]

FYi, this code works on bleeding edge (available in 5-10 days)

[DaryeDev]

Perfect, should be just updating the worker library, then. Thanks!

[raininglemons]

Is there any where public these kind of releases can be tracked?

[vicb]

Is there any where public these kind of releases can be tracked?

We'll give an update here when the changes are deployed.
The current status is that all changes have been merged,
it will take a few days before this reaches wrangler and prod.

[vicb]

As promised, here is an update:

workerd now implements node:timers and node:net (thanks @anonrig).

wrangler 3.106 which was just released contains the latest version of workerd.

Meaning that you should be able to use mongodb from your node apps!

Please test and report your experiences!

🙏

edit:

You need to use the nodejs_compat compatibility flag with a compatibility date set after 2024-09-23.

I have tested with:

# wrangler.toml
compatibility_date = "2024-12-05"
compatibility_flags = ["nodejs_compat"]

[tobsn]

they're already working on that @DylanBulmer - see 2 messages above yours

[Imtiajrex]

@JetLua @vicb I'll be working on adding TLSSocket.

any progress on the tlssocker?

[anonrig]

I've opened a PR but it's in progress. #3594

[anonrig]

TLSSocket and connect() has landed into main. It will be available to the general public in the next couple of weeks.

[alexbevi]

Very exciting @anonrig

[vicb]

/cc @alexbevi ☝️

[alexbevi]

Thanks for flagging @vicb. I've been following along closely and looking forward to testing this out now that the latest workerd is released with additional Node API support.

[ai-slave]

The moment i finally give up and switch to D1 from mongo you release THIS. But big thank you for finally doing this!!

[dustinsherwood]

Same

[ricky11]

how is your experienced moving to d1 from mongo? d1 is sql i believe. must be low latency for all over the world?

[equalogix]

I want to raise another related issue. First off there is a workaround see: mongodb polyfill
I have been using it in development since it was published and it mostly works. However, there is a bug that occurs when making certain requests, Mongodb throws: BSONOffsetError. I believe it is caused when the requests to the database returns a large object. In my case I get the error when making $vectorSearch request and getting back many documents. The exact error is:
Mongodb vector search error: BSONOffsetError: Parsed documentSize (10568 bytes) does not match input length (4075 bytes). offset: 0
I'm guessing that this error is not specific to the polyfill and will arise even when TLSSocket issue is resolved.

Another important point:
I am developing my app using ReactRouterv7, if I run the app locally using the react-router dev (basically using node-js), I don't get the errors. But if I run locally using wrangler dev or if I deploy the app, then I get the errors.

@alexbevi, seeing as you are from Mongodb, do you have any insight about this error, have you encountered it? The BSONOffsetError object itself is marked as experimental in the Mongodb Docs.

Finally I'm not the only one that is getting these errors, see polyfill issue 4

[equalogix]

I was wrong, this bug has everything to do with the polyfill. But the good news is that I fixed it, and I am now able to use MongoDb Atlas from my Cloudflare worker in preview and production. I have made a pull-request in the polyfill's repo with changes, waiting for it to be reviewed and merged.

[alexbevi]

Thanks for staying on top of this @equalogix. I haven't had a chance to test the polyfills again (hopefully can do that soon), but FYI #3594 is currently being worked on as well (which should hopefully be the last piece of the puzzle to getting this working natively in workerd)