MongoDB
Why
- Dynamic query
- Content is stored as documents
- Big database that need to be very fast
- Properties are stored like query and index
- Can be used for voting system, CMS or comment storage
Cassandra
Why
- When you make a lot of updates and insert
- Reading data is not the main scope of the database (writes are faster than reads)
- Content is stored as column
- High availability
- Can be used with success for logging
- Financial industry or any place where we work with a lot of data that is needed to be written
- Basket of an e-commerce application
CouchDB
Why
- For data that don’t change very often (insert and read and NOT update)
- We have a lot of predefined queries and we need versioning support
- Is a great database for CMS and CRM.
HBase
Why
- When you do data analyzing
- Works great in combination with Hadoop
Membase
Why
- When we need high concurrency
- When the latency is very low and we want the latency to be minimal
- Backend of a game or a system that offer data in real time
Redis
Why
- When we need to make a lot of updates
- When the database is not too big and can be kept in memory
- Can be used when we have a real time communication, for example a stock market with prices
0 comments:
Post a Comment