r/mongodb • u/keule_3000 • Sep 09 '24
Fuck you MongoDB NSFW
We have spent the past two years developing an enormous app to get a deprecation notice shortly before release. Get fucked MongoDB, we already are.
r/mongodb • u/keule_3000 • Sep 09 '24
We have spent the past two years developing an enormous app to get a deprecation notice shortly before release. Get fucked MongoDB, we already are.
r/mongodb
•
u/Effective_Opinion236
•
Dec 22 '25
I started building this tool (VisuaLeaf) over a year ago as a small passion project.
After graduating in 2024, the job market hit really hard. I spent months sending applications, doing interviews, getting ghosted, and watching friends struggle too.
At some point I realized I could either keep waiting for the right opportunity…or turn this little tool I've been tinkering with into something real. So I committed fully. Since then I’ve been working 80-90 hour weeks designing and rebuilding a MongoDB Desktop GUI from scratch.
It started as a tool just for me. Now it’s finally at a point where I feel brave enough to show it publicly for the first time.
I put together a compilation of short demos — each clip is quick and focused on core interactions, not every menu or workflow.
Feedback is super valuable — just comment or DM me and I’ll share access.
Other Features
Undo/Redo Operations: ctrl+z support for edits, inserts, deletes
Tasks: Import/Export data to other collections / JSON / CSV / mongodump
Shell: Direct access to Mongo shell
Save Script/Queries: Save queries from aggregation or shell pages
Index Manager: Create different types of indices for collections
(04/01/2026) For a full overview: https://youtu.be/WNzvDlbpGTk?si=6b9osXwOejre9fI3
Edit (01/14/2026):
visualeaf.com is now the landing page for the application (Not the same website as before ) .
The landing page is live!
Just to clarify since a few people asked, there is a community edition that allows can download and use whenever you want. There is a 14 day pro trial as well (no payment info required)
r/mongodb • u/BLochmann • Nov 14 '25
r/mongodb • u/Any-Ear-6479 • Sep 09 '24
Just received this email, not sure about others but this is certainly a blow when you’ve based your entire product on the Realm Sync SDK
r/mongodb • u/bindradugow • Jul 02 '24
Managing permissions in MongoDB has become a huge pain for us. We have dozens of instances (both hosted and self hosted). Trying to automate the provisioning process that today I do manually - creating roles, assigning them and so on.
r/mongodb • u/[deleted] • Nov 03 '20
I want to share with everyone here promotional codes that I found for MongoDB Atlas that will give you $410 $610 $810 in FREE MONGODB credits, here are your codes:
GETATLAS - $100 FREE
GOATLAS10 - $10 FREE
JOEK100 - $100 FREE
AARON200 - $200 FREE
ADO200 - $200 FREE
LAUREN200 - $200 FREE
Any others that I am missing that you have verified today to be working? There are a lot online right now that aren't working, looking for working codes as of 11/3!
Show your appreciation by upvoting this and helping others get $810 free from MongoDB to try/use the Atlas product. It's actually very good despite where it is hosted.
r/mongodb • u/Crescitaly • Mar 03 '26
I've been running a Node.js platform on MongoDB Atlas for over 2 years now. Solo dev, no DBA, just me figuring things out the hard way. Here are the costly mistakes I made and what I do differently now:
1. Not using compound indexes from day one I had individual indexes on fields I was querying together. Queries that should've been <10ms were taking 200ms+. One compound index on {userId: 1, createdAt: -1} cut my most common query from 180ms to 3ms.
2. Using $lookup everywhere instead of embedding I came from a SQL background and normalized everything. 5 collections for what should've been 2. Every page load was doing 3-4 $lookups. Once I denormalized the hot paths, response times dropped 70%.
3. Not setting maxPoolSize properly Default connection pool was way too small for my workload. I was getting timeout errors under moderate load. Setting maxPoolSize: 50 and minPoolSize: 10 with proper retry logic solved it.
4. Ignoring the aggregation pipeline for analytics I was pulling entire collections into Node.js and processing in memory. For 500K+ documents, this was destroying my server. Moving the logic to aggregation pipelines reduced memory usage by 90% and was 5x faster.
5. Not using Atlas Search instead of regex I had $regex queries for user search that were doing full collection scans. Switching to Atlas Search with a simple text index made search instant and the UX went from painful to great.
6. Forgetting TTL indexes for temporary data Session data, OTP codes, temp tokens — I was running a cron job to clean these up. A TTL index on expiresAt made this automatic and eliminated an entire service.
7. Not monitoring slow queries in Atlas The Performance Advisor in Atlas is free and incredibly useful. It literally tells you which indexes to create. I ignored it for months and was essentially flying blind.
The biggest lesson: MongoDB is not a SQL database with JSON syntax. The moment I stopped thinking in joins and started thinking in documents, everything clicked.
What MongoDB mistakes did you make early on? Would love to hear what others learned the hard way.
r/mongodb • u/NoInteraction8306 • Feb 05 '25
r/mongodb • u/yonootz321 • Sep 13 '21
I own a fintech startup focused on stock investments. As part of the background processing, we have to handle over 22M datapoints.
In order to retrieve the data for ticker symbols, a couple of thousands of records need to be selected (one datapoint for each day over the past few years). As you may imagine, selecting these datapoints is expensive in terms of runtime. It can take up to 8 seconds for symbols with lots of history (e.g. IBM or MSFT).
In order to improve the runtime, I performed a bunch of optimizations:
Pre-cache the entire data series for a ticker in a single record and invalidate the cache when a new datapoint becomes available (once per day).
Use aggregations and projections to select only the range/datapoints I'm interested in
Index the pre-cached records by symbol/exchange for faster retrieval
Group operations for the same symbol one after another to take advantage of the native mongodb memory caching of frequent results.
After all the above optimizations, I managed to reduce the latency for some of the background tasks from 8-15 sec to a staggering 30-80 ms, a 99.7% reduction.
Let's just say that MongoDB never ceases to impress me. The fact that I can retrieve the data in under 100ms is absolutely amazing.
If you're interested, I'm documenting all the performance optimizations, business decisions, milestones and other interesting facts on indiehackers here https://www.indiehackers.com/product/statfolio
r/mongodb • u/ralfv • Mar 24 '22
r/mongodb • u/rowlanosht • Mar 13 '24
r/mongodb • u/teheditor • Sep 18 '25
MongoDB has extended its search and vector search capabilities to Community Edition and Enterprise Server, opening up features previously limited to the Atlas cloud platform. MORE.
r/mongodb
•
u/TheDecipherist
•
Feb 16 '26

I keep seeing the same arguments recycled every few months. "No transactions." "No joins." "Doesn't scale." "Schema-less means chaos."
All wrong. Every single one. And I'm tired of watching people who modeled MongoDB like SQL tables, slapped Mongoose on top, scattered find() calls across 200 files, and then wrote 3,000-word blog posts about how MongoDB is the problem.
Here's the short version:
Your data is already JSON. Your API receives JSON. Your frontend sends JSON. Your mobile app expects JSON. And then you put a relational database in the middle — the one layer that doesn't speak JSON — and spend your career translating back and forth.
MongoDB stores what you send. Returns what you stored. No translation. No ORM. No decomposition and reassembly on every single request.
The article covers 27 myths with production numbers:
Transactions? ACID since 2018. Eight major versions ago.
Joins? $lookup since 2015. Over a decade.
Performance? My 24-container SaaS runs on $166/year. 26 MB containers. 0.00% CPU.
Mongoose? Never use it. Ever. 2-3x slower on every operation. Multiple independent benchmarks confirm it.
find()? Never use it. Aggregation framework for everything — even simple lookups.
Schema-less? I never had to touch my database while building my app. Not once. No migrations. No ALTER TABLE. No 2 AM maintenance windows.
The full breakdown with code examples, benchmark citations, and a complete SQL-to-MongoDB command reference:
10 years. Zero data issues. Zero crashes. $166/year.
Come tell me what I got wrong.

r/mongodb • u/Effective_Opinion236 • Jan 14 '26
A few weeks ago I shared a demo of VisuaLeaf, a MongoDB GUI I’ve been building, and the feedback from this community was incredible - thank you all!
This short video is a compilation of quick demos showing a few additional features that weren’t in the original demo - each clip highlights core interactions, not every menu or workflow.
I also put together an early documentation page since a few people asked about workflows and setup - it’s still evolving, but should help anyone who wants to dig deeper.
Docs: https://visualeaf.com/docs/
A few people asked what’s coming next, so I wrote a lightweight roadmap outlining post-launch plans like the advanced query builder and other improvements. It’s all on the same site, with a version now available. https://www.visualeaf.com
I’ll also be attending the MongoDB Locals event in SF on the 15th - excited to meet some of you there if I get the chance!
I really appreciate all the early feedback and encouragement from this community — it’s helped push the project across the finish line.
r/mongodb • u/MandemDontHearMeTho • Jan 13 '21
So much disinformation from SQL boomers
can’t do joins
Yes you can do left outer joins with $lookup
there is no schema. that’s crazy
I’ve never worked on an app using mongo that had a single collection without a schema. Never seen a collection not use a schema.
you can’t store relational data
You can literally architect a MDB exactly the same way as SQL if you wanted to, but there’s just no reason to because you’ll be able to nest certain data so you won’t need a 1000 table DB that only the person who built it understands
I need ACIDtransactions for my app
it has those
you’ll lose your data
Literally will never happen if you’re running a relevant sized cluster on atlas. Plus free automated backups. Plus elastic search quality FTS with atlas search.
———-
I feel like the MDB team, which is now publicly funded with a huge market cap, is just slowly chopping away at all these objections (ACID transactions was a big update)
Unfortunately there’s just so much misinformation left over from 2012 that SQL boomers parrot... many who have never even used used mongo they just read another SQL boomers hater blog post in 2012 and act like they’re not smol 🧠
r/mongodb • u/TheDecipherist • Feb 25 '26

I ran self-hosted MongoDB replica sets on AWS EC2 for about a decade. Six m5d.xlarge instances running Ubuntu. Two 3-member replica sets, one US, one EU, serving 34 branded e-commerce websites from a single codebase, processing millions of requests monthly with real-time ERP integration across 10,000+ SKUs. Zero data loss over the entire period.
I recently moved my current projects to Atlas, so I figured I'd write up the biggest lessons while they're still fresh.
This wasn't ideological. Atlas pricing for our storage and throughput requirements was pushing past $2K/month. On EC2 m5d.xlarge instances with local NVMe storage, we got better performance for a fraction of that. The tradeoff was simple: every upgrade, every backup, every failure at 2 AM was on us. For a decade, that tradeoff was worth it.
Six EC2 m5d.xlarge instances running Ubuntu. Three-member replica set in the US. Three-member replica set in the EU. Docker Swarm orchestrating 24 application containers alongside the MongoDB instances. Node.js app servers, nginx with ModSecurity compiled from source, Postfix, a 3-node Elasticsearch cluster with custom ngram analyzers, and DataDog for observability. MongoDB was installed directly on the OS, not containerized. The app layer was containerized. The database layer was not. That was deliberate.
bindIp will waste your first afternoon. Fresh MongoDB install on Ubuntu binds to 127.0.0.1. Your replica set members can't see each other. Sounds obvious when you read it here, but I've watched experienced engineers lose hours on this. You edit /etc/mongod.conf, add the instance's private IP to bindIp, restart. Done. The docs don't make this as prominent as it should be for a step that blocks literally every self-hosted deployment.
WiredTiger will eat your server alive. Year two of production. WiredTiger defaults to 50% of available RAM for its cache. On a 16 GB m5d.xlarge, that's 8 GB claimed by MongoDB before your application processes get anything. Our Node.js workers got OOM-killed during a traffic spike. MongoDB was doing exactly what it was configured to do, we just didn't configure it. Set wiredTigerCacheSizeGB explicitly. On shared instances, cap it at 40% of total RAM and leave room for the OS page cache. We were also running Elasticsearch on the same infrastructure, which also wants 50% of RAM for JVM heap, so memory planning became a survival skill.
The OS update that broke replication. A routine apt upgrade pulled in a new OpenSSL version that changed TLS behavior. Replica set members couldn't authenticate. The fix: pin MongoDB and all its dependencies. Never let automatic OS updates touch the database layer. Every MongoDB version change is a deliberate, tested event. Never a side effect of maintenance. After that night I wrote a runbook that still exists somewhere on a wiki nobody reads.
The index that replaced a hardware upgrade. Products collection, 10,000+ SKUs, powering the catalog for all 34 sites. Response times degrading. The team's instinct was to move to bigger instances. I ran explain("executionStats") on our top 10 queries. Three were doing COLLSCAN, not because we had no indexes, but because we had single-field indexes that didn't match our compound query patterns. One compound index dropped the worst query from 340ms to 2ms. The instance size was never the problem. Before you scale hardware, run explain() on your most frequent queries. If you see COLLSCAN, fix your indexes before you touch your infrastructure.
Running replica sets across the US and EU sounds clean on a whiteboard. In production it has sharp edges.
Election timeouts. The default electionTimeoutMillis assumes low-latency networks. Cross-Atlantic latency is 80-120ms on a good day. We had unnecessary elections during normal network jitter until we tuned this. If you're running cross-region, increase it. The default is too aggressive.
Write concern math. w:"majority" means the write has to cross the Atlantic before acknowledging. That's roughly 100ms added to every majority write. We split write concern by data criticality:
Orders, customer data, inventory: w:"majority" (can't lose it)
Sessions, caches: w:1 (regenerated easily)
Analytics events: w:1 (losing a data point doesn't matter)
That single decision, matching write concern to data criticality instead of applying one setting globally, was probably the most impactful performance optimization we made across the entire platform.
Oplog sizing. Cross-region secondaries lag during write bursts. If your oplog window is too small, a secondary can fall off the end during peak traffic and need a full resync. Oversize your oplog. The storage cost is trivial compared to the cost of a resync on a production replica set.
Daily: mongodump --oplog against a secondary, never the primary. Compressed and shipped to S3 in a different region.
The --oplog flag matters. Without it you get a point-in-time snapshot at whatever moment the dump started. With it you can replay operations forward to any specific second. Someone runs a bad aggregation pipeline that corrupts data at 2:47 PM? Restore to 2:46 PM. Without oplog capture you're stuck at whatever time the last dump completed.
Monthly: restore to a staging environment. A backup you've never tested is not a backup. We caught two corrupted dumps over ten years that would have been invisible without restore testing. Two dumps out of roughly 3,650. That's a 99.95% success rate, and the 0.05% would have been catastrophic if we'd discovered it during an actual failure.
My current projects don't need six EC2 instances. The workloads are smaller, the team is smaller, and Atlas in 2026 is dramatically better than Atlas was when I started self-hosting. The math flipped. If Atlas costs less than the engineering hours you'd spend managing self-hosted infrastructure, use Atlas. For us at scale with 34 sites and cross-region requirements, the economics went the other way for a long time. Both paths are valid depending on what you're running.
Curious what others are running. Self-hosted? Atlas? Hybrid? What does your replica set topology look like?
I wrote a more detailed version of this with full configs, TLS setup, Docker Swarm deployment, and step-by-step replica set initialization if anyone wants the link. Happy to drop it in the comments.
r/mongodb • u/alexbevi • Sep 26 '25
Hey everyone 👋, as one of the co-authors of the newly published High Performance with MongoDB I just wanted to share that if you're looking for a copy they're now available.
I did a quick blog post on the topic as well, but if you're a developers, database administrator, system architect, or DevOps engineer focused on performance optimization with MongoDB this might be the book for you 😉
r/mongodb • u/InActiveF • Sep 09 '24
Due to the depreciation of various MongoDB's extremely useful features, I feel it's best to have a discussion about the better alternatives for device sync. I've built an app around Device Sync, but I am now at a stand-still and I'm sure many are as well..
Please, if you've had any good experiences with alternatives, share them with the community for thoese who don't know to help guide us in the right direction.
r/mongodb • u/Didicodes • Sep 17 '25
r/mongodb • u/techbelle • Dec 23 '22
Hi there! I'm hoping to gather some feedback on the MongoDB documentation and if you have any time, please feel free to answer a few quick questions. Thank you all and happy holidays.
(Also, always happy to answer any questions about MongoDB)
r/mongodb • u/mrtehseen • Jan 07 '20
I found these few MongoDB Atlas credits codes which will give you over $500 worth credits.
NRABOY200, PROVISIONING, MONGODB4DOT2, GETATLAS, CLOUD2018, NEWREGION
Added few more, courtesy of people in replies.(Edited)
MAXIME200 & WF200
HAPPYNEWYEAR2020
If you are new to it or have smaller needs, they will help you a lot. :)
I redeemed mine.
r/mongodb • u/Standard_Parking7315 • Sep 28 '26
And how this guy can get away doing this 3 times in a row?
Why would Meta hire someone with these in their records?