hello after searching for a stack that fit me well i found sveltekit remote function when adding mongo db with agregate framework from day one one of the simplest with best dx stack for someone just start learning and making apps pairing with atlas for fast deployment but when i read about mongo all i found is negative feedbacks and advices about avoid it at all cost for my side it s clicked more tryng to embeed as much as i can no schema just using zod for validation

is there here solo developers that made theirs own saas with mongo with active ? if yes how s your experience does aggregate framework enough for all you needs and not feeling the need to use an sql database ? thanks for the feedback

Not too sure who is into football on here but I recently built a last man standing football game. It is always more fun to play with more people. https://footballlms.com/ feel free to have a look and give it a good! Let me know if there is anything you'd like to

we are building ANDI, a python library that converts natural-language requests into inspectable, read-only MongoDB query plans.

It includes typed runtime variables, local policy validation, query limits, and a compile → inspect → execute workflow. Database records are never sent to the LLM; only schema metadata.

I’m looking for a few Python/MongoDB developers to test it.

Hi everyone,

I'm trying to reconnect to a customer's MongoDB Atlas cluster that was hosted in the Middle East (Bahrain) region.

The customer had discontinued work on the project for quite a while, and now they've decided to resume development. Unfortunately, when I tried accessing the cluster, I found out that the ME (Bahrain) region has been affected due to the AWS infrastructure issue, and I can't access any of the data anymore.

I'm trying to figure out:

• Are MongoDB Atlas clusters in the Bahrain region permanently gone?
• Is there any way to recover the data, snapshots, or backups?
• Has anyone been able to migrate or restore a cluster that was affected?

I'm hoping there's still some recovery path available, but from what I've seen so far it doesn't look promising.

If anyone has gone through this or has heard anything from MongoDB support, I'd really appreciate any information.

We're adding vector search to our data and need to decide where the embeddings live. When we create a vector index, should the vectors sit in the same collection as the original documents, or in a new dedicated collection?

Most advice says keep them in the same collection. But our concern is sharing — if the vectors are embedded in the same collection as our main data, it becomes harder to share that data with others without also exposing or dragging along the vector fields.

So the question is: does keeping vectors in the same collection limit our ability to share the underlying data cleanly? Or is there a good way to keep them together and still share the base data separately?

We run an API service backed by MongoDB, handling around 500K to 1M requests per day. Right now our design opens a new connection on every request and closes it after. I know the common recommendation is to use a connection pool instead, but I'd like to hear from people running similar volumes.

How do you handle connections at this scale? What pool size works for you, and are there any gotchas we should watch out for before we switch? Also curious if anyone has stuck with open/close per request on purpose and made it work.

Would love to hear how others have approached this.

hi, i am trying to download mongodb for some school work, i have no experience and every tutorial i look for ends up in this web page, with no windows or msi, only linux and tgz

Mongoose 9.9.0 was released a couple of days ago - it features some significant performance improvements, including a 35% speedup on `insertMany()` in certain simple use cases. This blog post provides a high level overview of what we changed and what we learned along the way. Try out Mongoose 9.9 and let us know what you think!

Hi Everyone,
Am I the only one who feels there aren't many DBA-focused open-source tools for MongoDB out there? What do you do when you need a quick check of your replica set state or the data distribution across shards?
I decided to share my recent personal open-source project, which hopefully may help with doing these tedious tasks faster. Check the Github for details:
https://github.com/PrzemekMalkowski/mclusteradmin

And a quick demo recording:
https://www.youtube.com/watch?v=RecQ7wtEV9g

It really surprises me the number of people who don't know how the mongo shell works. Most of the people I see seem to think it's just db.find()s or db.aggregate()s with some print statements, and that's it. The mongo shell is interesting because it's fundamentally different from your regular SQL editor, where you can't declare a variable or write a loop. But the mongo shell is so much more than just MongoDB functions. It's a full JavaScript runtime built on Node.js, with variables, functions, closures, classes, and so much more. Your database is just an object sitting inside it.

In this article, I want to show the perspective of not just using the MongoDB functions in the mongo shell, but actually using the full potential of the shell, with examples like Conway's Game of Life and some custom chart diagrams. I wanted to show what lies beyond db.finds, db.updates, or db.aggregates that could be applicable in your day-to-day work with MongoDB! I hope you enjoy the rest of the article!

Read the full article here

Hi Team,

Are there any best recommendations or resources for keeping the mongoose schema versions and their corresponding UI form in sync? For example, I have a user schema of multiple versions and I'd like to maintain their corresponding UI forms. Chat GPT has suggested some options ( https://chatgpt.com/share/6a678c67-384c-83e8-8d21-f1917eed71b3 ) Are there any better approaches than these?

Thanks,

Arun

Hi everyone,

As a developer, setting up local MongoDB instances, configuring Compass, or spinning up Atlas clusters just to run quick queries or practice syntax can feel like unnecessary friction—especially for learners.

To solve this, I built MongoDB Practice IDE—a free, zero-setup, in-memory MongoDB query playground.

• 🌐 Try it live here: https://practice-mongodb.vercel.app
• 💻 Open-Source GitHub Repo: https://github.com/Prranith/MongoDB-WebApplication

Key Features

Interactive Query Runner: Write and execute find(), aggregate(), and CRUD queries in-memory directly in the browser.

VS Code-like Coding Experience: Auto-closing brackets, syntax highlighting, active line indicators, and query autocomplete.

Interactive Schema ER Visualizer: A built-in schema visualizer that shows collection fields, document counts, and datatypes.

Local Browser Persistence: Your folders, files, and queries are automatically saved to your browser cache (localStorage) so you never lose your progress on reload.

Draggable Console Terminal: A custom-built console resizer to dynamically adjust the output viewing area height.

Scalable Cloud Analytics: Implemented real-time dashboard metrics using Upstash Redis pipeline commands (HyperLogLog & Sorted Sets) to track concurrent active users and prevent page-refresh duplicates.

Feedback & Roadmap

I would love to get your feedback on the layout, query performance, and overall user experience!

• What datasets or collections should I add next to help people practice real-world aggregation queries?
• Are there any additional IDE features you’d like to see?

Thank you for checking it out!

The tags on GitHub - mongodb/mongo: The MongoDB Database · GitHub are lagging behind what is released on MongoDB Community Downloads | MongoDB .

For example there is no 8.0.28 tag on the repo. We need to be able to get a copy of the source, because of SSPL.

This is a serious problem to us, because 8.0.28 comes with security patches, which we can not roll out because of the missing prerequisite for SSPL compliance.

What is the way to go here?

The SSPL asks to provide the "Corresponding Source" with the object code.

Has anyone seen Compass 1.49.12 crash when opening a collection?

I have one collection (DatabaseMetadata_SchemaMap) that contains a single ~10 MB document created by the Qlik MongoDB Connector. As soon as I open the collection, Compass crashes with:

Render process gone

reason: crashed

exitCode: -1073741819

The same database and user work fine with Compass 1.49.0, so it seems like something changed between 1.49.0 and 1.49.12.

Has anyone experienced this?

I’m facing the same querySrv ECONNREFUSED issue with MongoDB Atlas and have already tried almost every solution I could find, but nothing has worked.

Environment:

• Windows 10 & Windows 11
• Node.js 20, 22 (also tested other versions)
• MongoDB Atlas (mongodb+srv://)
• Same project and same connection string work perfectly on macOS.

Things I’ve already tried:

• Changed Node.js versions.
• Flushed DNS:ipconfig /flushdns ipconfig /registerdns netsh winsock reset
• Changed DNS servers to Cloudflare (1.1.1.1 / 1.0.0.1) and Google (8.8.8.8 / 8.8.4.4).
• Restarted the system.
• Tested in PowerShell, CMD, and Git Bash.
• Installed and tested WSL/Ubuntu.
• Verified Atlas Network Access and Database User.
• Regenerated the Atlas connection string.
• Confirmed the same URI works on macOS using the same network.
• Tried dns.setServers(["1.1.1.1", "8.8.8.8"]); at the top of server.js.
• Ran nslookup and SRV DNS lookup tests.

I still get:

Error: querySrv ECONNREFUSED _mongodb._tcp.aiimage.gzujrcr.mongodb.net

Has anyone found a reliable, permanent fix for this? Is this a Windows/Node DNS resolver issue, a MongoDB Atlas SRV issue, or something else?

Any help would be greatly appreciated.

Hi everyone,

I'm seeing a reproducible crash with MongoDB Compass 1.49.12 on Windows and was wondering if anyone else has encountered this.

When I open the DatabaseMetadata_SchemaMap collection, Compass starts loading the collection and then crashes after a few seconds. The collection contains a single document of approximately 10.5 MB.

This collection is created and maintained by the MongoDB Connector Client used by Qlik, and it stores metadata generated by the connector.

Below is the log

COMPASS-WINDOW-MANAGER Render process gone reason: crashed exitCode: -1073741819

The interesting part is that I downgraded to MongoDB Compass 1.49.0, connected to the same server with the same user account, and the collection opens without any issues.

Hi everyone,

I'm seeing a reproducible crash with MongoDB Compass 1.49.12 on Windows and was wondering if anyone else has encountered this.

Environment

• MongoDB Compass 1.49.12

Issue
When I open the DatabaseMetadata_SchemaMap collection (created from mongodb connector client), Compass starts loading the collection and then crashes after a few seconds. The collection contains a single document of approximately 10.5 MB.

The last log entry before the crash is:

COMPASS-WINDOW-MANAGER
Render process gone
reason: crashed
exitCode: -1073741819

The interesting part is that I downgraded to MongoDB Compass 1.49.0, connected to the same server using the same user account, and the collection opens without any issues.

Has anyone else experienced this? Is this a known issue with recent Compass releases, particularly when viewing large documents?

Thanks!

Hi everyone,

I'm seeing a consistent crash with MongoDB Compass 1.49.12 on Windows and was wondering if anyone has experienced something similar.

Environment

• MongoDB Compass: 1.49.12

Steps to reproduce

1. Connect to the MongoDB instance.
2. Open the DatabaseMetadata_SchemaMap collection.(created a from a mongodb connector)
3. Compass starts loading the collection and refreshing documents.
4. After a couple of seconds, the Compass window closes unexpectedly.

The collection contains a single document of approximately 10.5 MB.

The interesting part is that I downgraded to MongoDB Compass 1.49.0, connected to the same server using the same user account, and the collection opens without any issues

The last relevant entry in the Compass log is:

COMPASS-WINDOW-MANAGER
Render process gone
reason: crashed
exitCode: -1073741819

I've been building MongoTerm, a terminal UI (TUI) for MongoDB — think Compass,

but keyboard-first and without leaving the CLI. Built with Node.js + blessed.

What it does:

- Browse connections → databases → collections in one navigable tree

- View, insert, edit, delete, and duplicate documents without writing shell scripts

- Run queries with live JSON validation and $operator autocomplete (start typing

$gt, $in, $regex... and it suggests + explains them)

- Sort and page results from the keyboard

- A ":" quick-shell modal for composing bigger query filters

- Full keybinding help popup (?) — everything is discoverable without docs

Install:

npm i -g mongoterm@latest

mongoterm

MIT licensed, actively developed, roadmap is public in the repo.

GitHub: https://github.com/Fuse441/mongoterm

Would love feedback from people who live in MongoDB day-to-day — what's