Architecture Notes

Sweet spot#

10K–500K documents with intelligent caching. Good fit for:

• Desktop apps (Electron, Tauri)
• CLI tools
• Embedded systems
• Rapid prototyping
• Local-first applications
• Node.js apps needing local storage without a server

Where it stops being the right tool#

• 10M+ documents, or datasets that need to scale past a single node — use PostgreSQL, MongoDB, or SQLite.
• Multi-user web applications with hundreds of concurrent connections — AxioDB is single-instance, not client-server. AxioDBCloud adds remote TCP access for service-to-service calls, but the instance itself is still one process.
• Relational data with JOINs and foreign-key constraints — AxioDB is document-based NoSQL, not relational.
• Distributed systems needing replication, sharding, or clustering — AxioDB is single-node only.
• Cross-collection ACID transactions — transactions are scoped to a single collection.

Migrating to PostgreSQL or MongoDB when you outgrow AxioDB is the expected path, not a failure of the tool — AxioDB was never trying to be a replacement for either.