FAQ

When should I not use DocumentForge?

It’s built for embedded scenarios, prototypes, and small-to-medium production workloads where a single dependency-free engine that scales from one file to a sharded cluster is the win. Reach for a different tool when you need a large multi-writer OLTP cluster, mature managed hosting, or an ecosystem of third-party integrations today.

Is it a replacement for MongoDB?

It speaks JSON documents and SQL-like queries, and covers a lot of the same ground for .NET apps — but it’s a focused engine, not a drop-in protocol clone. See the migration notes.

Does my data file survive an upgrade?

Yes. The on-disk format is versioned and stable; upgrading the engine over an existing .dfdb file is a no-op migration. Back up the file and flush cleanly before swapping binaries.

Is it production-ready?

DocumentForge passes a comprehensive test suite and has the architectural pieces you’d expect from a production system (WAL, checksums, crash recovery, replication, failover). It’s a 0.1 project — evaluate it for your workload.