NoSQL Databases:

An experience with

Jim Chang

Firstly, understand what is

MongoDB

MongoDB:

Collections of a lot of JSONs, literally

Scalability is excluded in this discussion

Pros (1/3): SchemalessNo need to design schema, always ready for different kinds of data, just put them in the bag

Perfect for dirty data warehouse!

Pros (2/3): Easiness

Strong Integration with programing languagesYou don’t have to learn another language

Postgresql in Python:cur.execute("SELECT * from bar")

Pros (3/3): MapReduceUltimate solution for complicated queries

A simple MapReduce snippet (1/2)

A simple MapReduce snippet (2/2)

Cons(1/3): RedundancyIt takes more space than SQL does,because of the repetitive fields

Cons(2/3): No Joins

Repetitive Design Relational Design

Not suitable for “Relational” data design

Why You Should Never Use MongoDB (Sarah Mei)http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/

Cons(3/3): No transactionsNo transactions, the default configuration is not for consistency-concerned issue. Be careful if you want to handle monetary data

MongoDB, E-commerce and Transactions (Steven Francia)http://www.slideshare.net/spf13/mongodb-ecommerce-and-transactions-10524960

1. Schemaless

2. Easiness

3. MapReduce

1. Redundancy

2. No joins

3. No transactions