-
Notifications
You must be signed in to change notification settings - Fork 184
Why MemDB
Yu Xia edited this page Aug 4, 2015
·
7 revisions
-
Performance : In memory data access, up to 25,000 ops/shard (tested on EC2 c4.xlarge).
-
Horizontally Scalable : Performance grows linearly by adding more shards.
-
ACID Transaction : Full ACID transaction support on distributed environment.
-
MongoDB Compatible : It's just a 'mongodb' with transaction support, built-in 'mongoose' support.
Comparison with other databases
| Database | Performance | Horizontally Scalable | Transaction Support | Data Structure |
|---|---|---|---|---|
| MySQL | Medium (Disk I/O) | No | Yes (InnoDB) | Row based |
| MongoDB | Medium (Disk I/O) | Yes | No (except some basic atomic modifier) | Object(BSON) |
| Redis | High (Memory) | Yes | No (.multi can do some 'transaction like' thing) | Very Elemental |
| MemDB | High (Memory) | Yes | Yes | Object(JSON) |