Guides
Task-oriented walkthroughs for the things people actually do with doc: CRUD and queries, indexes, transactions, the wire server, operations, and tuning.
Each guide is built around a job rather than a flag: putting documents in and getting them back out, indexing them so the planner can find them quickly, running multi-document transactions, serving the file to existing drivers, keeping a .doc file healthy, and making it fast.
They assume you have worked through the quick start.
- CRUD and queries: insert, find, update, delete, the MQL operators, and the aggregation pipeline.
- Indexes and query planning: single-field, compound, multikey, unique, sparse, partial, and TTL indexes, and reading a plan with Explain.
- Transactions and change streams: sessions, snapshot and serializable isolation, and tailing changes.
- The wire-protocol server: serving a
.docfile somongoshand the official drivers connect unchanged. - Operations: integrity checks, compaction, checkpoints, vacuum, online backup, WAL archiving, point-in-time restore, and moving data.
- Performance tuning: durability levels, the page cache, the columnar store, and the benchmark gate.
CRUD and queries
Insert, find, update, and delete documents, then query them with the MongoDB Query Language and the aggregation pipeline, all through the same API shape as the MongoDB Go driver.
Indexes and query planning
Create single-field, compound, multikey, unique, sparse, partial, and TTL indexes, and read the plan the cost-based planner picks with Explain.
Transactions and change streams
Run multi-document transactions under snapshot or serializable isolation with a session, and tail changes to a collection or database with a change stream.
The wire-protocol server
Serve a .doc file over the MongoDB wire protocol so mongosh and any MongoDB driver connect to it unchanged, with optional authentication and TLS.
Operations
Keep a .doc file healthy: integrity checks, compaction, checkpoints, vacuum, online backup, WAL archiving and point-in-time restore, and import and export.
Performance tuning
The knobs that matter: durability levels, the page cache, the columnar projection store for analytics, and the benchmark gate that guards against regressions.