1. Polyglot Persistence: Column Stores
Ryan CrawCour | Microsoft Program Manager
David Makogon | Microsoft Cloud Architect

2. Course Topics Polyglot persistence: choosing the right storage mix
01 | Data landscape
02 | Relational databases
03 | Key-value stores
04 | Document stores
05 | Graph stores
06 | Column stores
07 | Polyglot persistence

3. Agenda What is a column store? Why and Why Not? Options in Azure
Demo – Cassandra

4. What is a column store?

5. Column stores Not these columns:
Photo credit: Will Powell – “Nashville Parthenon – HDR”

6. What’s a column store?
Data is keyed by row (e.g. Twitter ID) Individual content stored as columns Groups of columns comprise a column family

7. Example: Weather data
Data is keyed by row (e.g. weather station ID) Columns may have standard or custom names For weather: Each col name = date
stationID
Timestamp
temp …

8. Why a column family? Why not?
Optimal:
Very large quantities of data
Queries well-known up-front
Scale and durability
Non-optimal:
Highly-relational data
Querying on many different properties

9. Options in Azure

10. Options in Azure?
Cassandra
HBase

11. Using Cassandra + CQL CREATE TABLE temperature ( stationID text,
   readingtime timestamp,
   temp text,
   PRIMARY KEY (stationID,readingtime) );
INSERT INTO temperature(stationID,readingtime,temp)
VALUES (‘1’,’ :00:00′,’45F’);

12. Finding temperatures SELECT readingtime,temp FROM temperature
WHERE stationID=’1’;

13. Cassandra

14. Summary

15. Summary What is a column store? Why and Why Not? Options in Azure
Demo – Cassandra