selecting the right nosql tool for the job

Choosing a NoSQL Solution

Thursday, August 25, 11

Dave GrijalvaDirector of Platform Technology


NoSQL


Why so many?


Tradeoffs


CAP Theorem

C

PA

Consistency

Partition Tolerance

Availability

Unpossible


Access Patterns

• How much content?

• How many operations?

• Ratios of Insert/Update/Read/Delete?

• How valuable is your data?


Schema and Indexing

• How will you access your data?

• User Requests vs Background Processing

• Secondary Indexes


Clustering

•Where is the sharding done?

• Adding and removing nodes

•Where (in the world) is your data?

• Failure cases


Operations

• Backup and recovery

• Multi-datacenter issues

• Ease of deployment

• Tools integration

• Support


NoSQL @ ngmoco:)


Start Simple

Load Balancer

API Server API Server API Server

MySQL MySQLMemcached


OAuth

• Shared secret based

• Signature validation on every request

• Tokens are per session

• Tokens expire


Redis

• In memory key/value store

• Really fast

• Delayed persistence

• Supports TTL per record

• Values can be blobs, lists, sets, or hashes


Game Data Store

• Per user, per game key/value store

• Exposed via REST API

• Very write heavy

• Keys are usually provided upfront

• High data throughput


Cassandra

• Configurable consistency

• No single write master

• Sharding managed by the cluster

• Built in replication

• Supercolumns!


“The Bank”

• High transaction volume

• ACID a requirement

• Lots of tracking required for revenue calculations

• Five nines uptime

• Insert dominant


Marklogic

• XML Document store

• Transactional

• Insert based persistence

• Temporal

• Clustered


Tips

• Start as simple as possible

• Learn how the systems work

• Try to find success and failure stories

• Explore failure scenarios. Test!

• There is no best solution. Look for a best match solution


ngmoco:) is hiring!ngmoco.com/careers


Questions?
