Skip to main content

3 posts tagged with "mongodb"

View All Tags

The Request You Made 100 Times

· 11 min read
Vladyslava Prykhodko
Engineering Technical Lead & Architect

A backend-for-frontend layer is one of the easier architectural decisions to get right. Each client gets a service that speaks its language, the domain services stay clean, and every team owns a box with a clear border drawn around it. An architect reviews the diagram and approves it — and the diagram is correct.

This is a field story about what the diagram doesn't show. Four correctly-written service calls, each behaving exactly as designed, turned one screen render into roughly a thousand queries against a sharded collection. The screen stopped loading, one collection's query time dwarfed every other collection in the cluster, and the ticket said "MongoDB is slow."

MongoDB was not slow. Nobody had ever counted what one user action actually costs.

The Hidden Complexity of "Easy" Geo-Sharding in MongoDB

· 8 min read
Vladyslava Prykhodko
Engineering Technical Lead & Architect

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.

The "Logical DB-per-Service" Pattern at Scale

· 3 min read
Vladyslava Prykhodko
Engineering Technical Lead & Architect
Ivan Baha
Software Team Lead & Architect

When building distributed systems, the "Database per Service" rule is often seen as a strict rule. The common instinct is to create a separate physical database cluster for each microservice to ensure full isolation. However, as your system expands, managing dozens or hundreds of independent database servers can quickly become an operational nightmare.