Alpha development. Does NOT yet work yet.
x.y = "foo"; (on registered instances) causes asynchronous persistance to disk.
See the examples for how easy it is to get started.
- Package not available yet - will be
npm install barricane-db
Reasons why BarricaneDB will never be a good fit for your application.
- Your data set is too big to fit in RAM.
- Your application needs ACID guarantees. BarricaneDB could loose 1-5 seconds of data on a process crash (OS dependent).
- Your application doesn't happily shard into BarricaneDB's one-DB-per-process design.
- You need to query your database from outside the NodeJS process - e.g. Crystal Reports.
Reasons why BarricaneDB is not currently a good fit.
- Your application needs a production-tested solution.
- You need good error handling.
- You need async database opening (persistence is already fully async).
- Transactions are important to you.