Yes, SQL! Uri Cohen

> SELECT * FROM qcon2010.speakers WHERE name=‘Uri Cohen’ +-----------------------------------------------------+ | Name | Company | Role | Twitter | +-----------------------------------------------------+ | Uri Cohen | GigaSpaces | Product Manager | @uri1803 | +-----------------------------------------------------+ 2 > db.speakers.find({name:”Uri Cohen”}) { “name”:”Uri Cohen”, “company”: { name:”GigaSpaces”, products:[“XAP”, “IMDG”] domain: “In memory data grids” } “role”:”product manager”, “twitter”:”@uri1803” }

Agenda 3 SQL What it is and isn’t good for NoSQL Motivation & Main Concepts of Modern Distributed Data Stores Common interaction models Key/Value, Column, Document NOT consistency and distribution algorithms One Data Store, Multiple APIs Brief intro to GigaSpaces Key/Value challenges SQL challenges: Add-hoc querying, Relationships (JPA)

A Few (more) Words About SQL 4

SQL (Usually) Centralized  Transactional, consistent  Hard to Scale 5

SQL Static, normalized data schema Don’t duplicate, use FKs 6

SQL Add hoc query support  Model first, query later 7

SQL Standard  Well known  Rich ecosystem 8

(Brief) NOSql Recap 9

NoSql (or a Naive Attempt to Define It) A loosely coupled collection of non-relational data stores 10

NoSql (or a Naive Attempt to Define It) (Mostly) d i s t r i b u t e d 11

NoSql (or a Naive Attempt to Define It) scalable (Up & Out) 12

NoSql (or a Naive Attempt to Define It) Not (always) ACID BASE anyone? 13

Why Now? Timing is everything… Exponential Increase in data & throughput Non or semi structured data that changes frequently 14

A Universe of Data Models 15 Key / Value Column { “name”:”uri”, “ssn”:”213445”, “hobbies”:[”…”,“…”], “…”: { “…”:”…” “…”:”…” } } { { ... } } { { ... } } Document

Key/Value Have the key? Get the value That’s about it when it comes to querying Map/Reduce (sometimes) Good for cache aside (e.g. Hibernate 2nd level cache) Simple, id based interactions (e.g. user profiles) In most cases, values are Opaque 16

Key/Value Scaling out is relatively easy (just hash the keys) Some will do that automatically for you Fixed vs. consistent hashing 17

Key/Value Implementations: Memcached, Redis, Riak In memory data grids (mostly Java-based) started this way GigaSpaces, Oracle Coherence, WebSphere XS, JBoss Infinispan, etc. 18

Column Based 19

Column Based Mostly derived from Google’s BigTable / Amazon Dynamo papers One giant table of rows and columns Column == pair (name and a value, sometimes timestamp) Each row can have a different number of columns Table is sparse: (#rows) × (#columns) ≥ (#values) 20

Column Based Query on row key Or column value (aka secondary index) Good for a constantly changing, (albeit flat) domain model 21

Document Think JSON (or BSON, or XML) 22 { “name”:”Lady Gaga”, “ssn”:”213445”, “hobbies”:[”Dressing up”,“Singing”], “albums”: [{“name”:”The fame” “release_year”:”2008”}, {“name”:”Born this way” “release_year”:”2011”}] } { { ... } } { { ... } }

Document Model is not flat, data store is aware of it Arrays, nested documents Better support for ad hoc queries MongoDB excels at this Very intuitive model Flexible schema

What if you didn’t have to choose? 24 JPA JDBC

A Brief Intro to GigaSpaces In Memory Data Grid With optional write behind to a secondary storage 25

A Brief Intro to GigaSpaces Tuple based Aware of nested tuples (and soon collections) Document like Rich querying and map/reduce semantics 26

A Brief Intro to GigaSpaces Transparent partitioning & HA Fixed hashing based on a chosen property 27

A Brief Intro to GigaSpaces Transactional (Like, ACID) Local (single partition) Distributed (multiple partitions) 28

Use the Right API for the Job 29 Even for the same data… POJO & JPA for Java apps with complex domain model Document for a more dynamic view Memcached for simple, language neutral data access JDBC for: Interaction with legacy apps Flexible ad-hoc querying (e.g. projections)

Memcached (the Daemon is in the Details) Memcached Client

Memcached Client Memcached (the Daemon is in the Details)

SQL/JDBC – Query Them All 32 Query may involve Map/Reduce Reduce phase includes merging and sorting

SQL/JDBC – Things to Consider Unique and FK constraints are not practically enforceable Sorting and aggregation may be expensive Distributed transactions are evil Stay local… 33

JPA It’s all about relationships… 34

JPA Relationships To embed or not to embed, that is the question…. Easy to partition and scale Easy to query: user.accounts[*].type = ‘checking’ Owned relationships only

JPA Relationships To embed or not to embed, that is the question…. Any type of relationship Partitioning is hard Querying involves joining

Summary One API doesn’t fit all Use the right API for the job Know the tradeoffs Always ask what you’re giving up, not just what you’re gaining 37

Thank YOU! @uri1803 http://blog.gigaspaces.com 38