Love between NoSQL & Polyglot persistance

nosqlbrainstorm

- polyglot data / persistance
  - nosql is a implementation of polyglot data
- types of databases
  - NoSQL[x]
    - key-value stories[x]
      - Riak
      - Memecache
      - Redis
    - document-oriented [x]
    - graph [x]
    - event stories
    - column [x]
- NoSQL
  - It's not about db it's about philospophy.
  - Performance
- Where we can use NoSQL
  - big sets of data.
  - real-time web.
  - high amount of users.
- CAP theorem [x]
- Advantage of NoSQL
  - very fast
  - do not require fixed schemas
  - avoid join operations
  - scale horizontally
  - Fault-tolerant
  - Predictable latency
  - quick and easy replication
- Side effect of NoSQL
  - eventual consistency
  - lack of ACID
- Distributed system can guarantee only two at same time
  - Consistency
  - Partition
- Define a conceptual data model
  - Right data model will accurately reflect data structure.
  - Good understanding of domain 
- MapReduce
- It's challenge to choose right persistance method.



references :
- http://en.wikipedia.org/wiki/NoSQL
- http://en.wikipedia.org/wiki/Database
- http://en.wikipedia.org/wiki/CouchDB
- http://en.wikipedia.org/wiki/Apache_Cassandra
- http://martinfowler.com/bliki/PolyglotPersistence.html
- http://blog.nahurst.com/visual-guide-to-nosql-systems