Navigating NoSQL in cloudy skies

Presented at:Chicago IT Architects GroupJan 15, 2013

shankar ramachandranworks with:Microsoft Web Stack of LoveMicrosoft SQL Serveralso works with:

Skippingessential steps,just creates anillusion ofspeed &growth.

simple. 5

Agenda• What NoSQL is & What it is not• Why NoSQL – 2 specific reasons• Conceptual Fundamentals & Grounding• 3 techniques to classify & choose• Way ahead

What• Variety of non- relational database systems• Usually schema-less• Mostly open-source• Not anti-RDBMS• Not a replacement

No – relational tables –were harmed in the making of this presentation.

Why NoSQL?

Reason #1

Big Data

“Big Data”

4 Vs of Big DataVolume Velocity• Terabytes and Petabytes • Time sensitive real-time data processing & decision makingVariety Value• Of structured and • Inherent value always unstructured data

RDBMS can handle all that. Right??• Scaling up has a limit.• Sharding - spread data across servers.• Denormalization - potentially duplicates data in the database, requiring updates to multiple tables when a. duplicated data item is changed• Distributed Caching - caching recently accessed data in memory and storing that data across any number of servers. or virtual machines. Think Memcached.

RDBMS tactics - Downside & Pitfalls• Re-sharding is disruptive.• Maintain schema on every server• Distributed Caching accelerates just the reads• You lose relational benefits anyway.

aggregate-oriented vs.aggregate-ignorant

Aggregate-orientation • Unit of data can have a more complex structure than a set of simple tuples. • Excellent fit to run on a cluster. • Atomic manipulation of single aggregate. • Application code takes precedence.

Reason #2

Impedance Mismatch

• Difference between relational model & in-memory data structures• Simple tuples• ORMs provide a bridge ; complicate query performance.

{ product : "Tintin Statue",created : Date(’11-16-2010’),title : "Brass replica of Tintin",tags : [ "tintin", "herge", "snowy"],comments : [{ author : ‘Shankar, comment : I love it },{ author : ‘Skeet, comment : me too!! } ] }

Concepts

3 properties of distributed databases• Consistency means that each client always has the same view of the data.• Availability - node always available for read and write.• Partition tolerance means that the system works well across physical network partitions.

consistency availability partition-tolerance only-2-out-of-3 CAP Theorem

consistency availabilitypartition-tolerance This is incorrect

consistency availabilitypartition-tolerance

horizontal-partitioning multiple-instances shared-nothing sharding

commodity-hardware distributed infinite-expansion horizontal-scalability

google-patented-framework map: chop data reduce: fold data MapReduce

low-latency order-of-reads delayed-gratification eventual-consistency

For the academically inclined: Proprietary DB high-performance Google App. Engine Google BigTable Amazon Dynamo Proprietary system high-availability AWS key-value

quick shout-out

Object orientedFaster and Declarative.Lack of interoperability and recovery standards. End-to-end development, database & deployment platform Embeddable and fast. Lack of querying capabilities.

XMLNative XML database systems.Typically XQuery used as querying mechanism.Advantage or Disadvantage based on XML affinity. Sedna Tamino

Choice By Data Model

aggregate-ignorant

GraphGraph-data structure associative-datasets node/edges Small records with complex interconnections. GraphDB

aggregate-oriented

Key/Valuein-memory processing/cachinghyper-efficient associative storage Voldemort

Wide-Columnhorizontally-partition fully distributed Dynamo + BigTable

Document-orientedschema-less collection-based-JSON-like dynamic-indexing

Choice By CAP CA AP CP RDBMS Riak MongoDB Dynamo Hbase Cassandra Redis CouchDB Hypertable Voldemort

C C++ C# Erlang JavaRedis MongoDB RavenDB CouchDB Cassandra Hypertable GraphDB Couchbase Hadoop Kyoto Riak HBase Tycoon Scalaris neo4J Voldemort

Way Ahead

What areMicrosoft &Oracle up to?

Microsoft Polybase

Oracle NoSQL

polyglot persistence … a highly possible future

We learnt that ...RDBMSs are here to stay. NoSQL is not creatinga paradigm shift.NoSQL provides a set of non-relation datastores & technologies that have affinity forbeing processed in a clustered environment.Some of them NoSQL databases also offer asolution to Impedance Mismatch thusincreasing application developer productivity.What Aggregate-Orientation in data modelingmeans.What the different types of database typesare.And most importantly ... we now know thatRDBMS systems need DBAs - DatabaseArchitects & Admins.NoSQL systems need DBAs too - DevelopersBeyond Awesome!

Twitter: @areshankar

Computers are useless. They can only give you answers. Pablo Picasso Cubist painter (1881 - 1973)?

Navigating NoSQL in cloudy skies

by shnkr_rmchndrn on Jan 16, 2013

Accessibility

Categories

Upload Details

Usage Rights

Statistics