NoSQL Systems:
Name | Type | Wiki Link | Groups |
---|---|---|---|
MongoDB | Document Store | - | zxyang, mwang5 |
Apache CouchDB | Document Store | - | akalinin, wenjun |
Apache Cassandra | Column Store / BigTable | - | jxfeng, xiaowei |
Apache HBase | Column Store / BigTable | - | zikaiwang, jcchin |
Membase | Key Value | - | sunilmallya, zuffi |
Redis | Key Value | - | jtavares, ckeith |
HyperTable | Column Store / BigTable | - | ljin, yanglu |
Tokyo Cabinet | Key Value | - | martins, kbambino |
Scalaris | Key Value | - | irina, gillmor |
Riak | Key Value | - | jdedona |
Each group is responsible for collecting information about their assigned system. Be sure to keep track of the sources/urls that you find. A rough outline of what is needed for each system is as follows:
- History
- Programming Language Interface
- Data Model + Operators
- Physical Structures (e.g., indexes, hash tables)
- Users + Applications + Target Workloads
- Transaction Support:
- Consistency Model
- Failure Model + Replica Management
- ACID Properties
- Elasticity + Data Redistribution
- Optimizations
- System Architecture
- Support for third-party systems:
- Why makes the system different from others?