2 posts tagged with "mongodb-atlas"

Geo-sharding is one of the features that makes MongoDB attractive for a global product. You keep each user's data physically close to them, one logical collection still reads as a single dataset in Compass or Atlas, and the adoption cost looks tiny: add a shard key, and queries route to the right region.

The simplicity is real. So is the failure mode hiding inside it. This is a field story about how "easy" geo-sharding quietly doubled a database bill — and why that was never MongoDB's fault.

Every AI chatbot has the same problem: it forgets you.

You tell it your name in one conversation, and by the next one it has no idea who you're talking to. You tell it your preferences, and a week later it's making things up. The bigger you build, the worse this gets — and at some point the bill from your LLM provider stops being funny too.

The fix has a name: RAG, short for retrieval-augmented generation. You give the model a memory it can search before it answers. The catch is that the standard way to build it is overcomplicated — a vector database, an embedding service, a chat model API, and a server somewhere to glue them all together. Four services, four monthly bills, four different things that can wake you up at 3 AM. Three months in, you're paying close to $200 a month for what is, honestly, a chatbot that remembers things.