kmp-mongodb-database

When to Use This Skill

Use this skill when you need to:

• Build or review a MongoDB-backed backend data layer for a KMP app
• Keep document mapping and repository code cleanly separated
• Use Flow or change streams for reactive reads
• Model typed database failures instead of leaking driver exceptions upward
• Scaffold repeated database setup for a new service

Recommended default: keep MongoDB on the server side behind a repository boundary, map documents to domain models at the edge, and expose typed errors to the caller.

Trigger keywords: MongoDB, database, collection, repository, document mapping, Flow, change stream, server-side Kotlin, coroutine driver, typed errors, backend data.

Freshness rule: the MongoDB Kotlin coroutine driver evolves independently of the JVM driver — recheck the official docs before upgrading or scaffolding.