1. The Death of Relational

2. [~] whoami
Arin Sarkissian
Platform Lead, Digg.com
arin@digg.com
http://new.digg.com/phatduckk
http://arin.me
http://twitter.com/phatduckk
The Death of Relational

3. No(My)SQL @ Digg The Death of Relational

4. Classic Rivalries The Death of Relational

5. Classic Rivalries The Death of Relational

6. Classic Rivalries The Death of Relational

7. Classic Rivalries The Death of Relational

8. Classic Rivalries The Death of Relational

9. SQL vs NoSQL The Death of Relational

10. Why NoSQL?
In ~15 Minutes or less
The Death of Relational

11. Operations & Scaling
The Death of Relational

12. “ Twitter likes the idea of processes that can
die and the cluster won't notice. We can
manage and correct it later without ops
having to hop-to because a server rebooted.
Jeff Hodges - Twitter
@jmhodges
Operations & Scaling The Death of Relational

13. • No single point of failure
• No “special” nodes
• Always writable
• Hinted handoff
• Read Repair
• Rebalance
• Easily add new nodes
• Bootstrap
• Remove nodes
http://wiki.apache.org/cassandra/ & https://wiki.basho.com/display/RIAK/
Operations & Scaling The Death of Relational

14. “ I know of one company that’s managing to
scale portions of their PostgreSQL servers
by purchasing $250,000 servers. This would
cover my 50 node EC2 cluster for two years!
Joe Stump - SimpleGeo
http://stu.mp/2010/03/nosql-vs-rdbms-let-the-flames-begin.html
Operations & Scaling The Death of Relational

15. No/Flexible Schema
The Death of Relational

16. “ ... making schema changes or adding
indexes to a database with more than 10
- 20 million rows completely locks the
database for hours at a time.
Bret Taylor - FriendFeed/Facebook
http://bret.appspot.com/entry/how-friendfeed-uses-mysql
No/Flexible Schema The Death of Relational

17. No/Flexible Schema The Death of Relational

18. No/Flexible Schema The Death of Relational

19. No/Flexible Schema The Death of Relational

20. SQL Can’t Do That
The Death of Relational

21. “ I wrote Dynomite because I had a
problem that existing database
management systems couldn't solve.
Cliff Moon
@moonpolysoft - Dynomite
SQL Can’t Do That The Death of Relational

22. • Store petabytes of data (distributed, w/ replication & fault tolerance)
• Parallelize computation across a bunch of machines
• Find the shortest path between 2 nodes
• “Find friends of friends whom I don’t know that are > 25 years old and like Punk Rock"
SQL Can’t Do That The Death of Relational

23. • Cool, client triggered replication/synchronization system
• Ability to serve an entire CouchApp (web app w/ data & CSS, JS etc)
• Store & perform operations on lists, sets, hashes & sorted sets
• Use as a publish/subscribe server
SQL Can’t Do That The Death of Relational

24. You Don’t Like SQL
The Death of Relational

25. You Don’t Like SQL The Death of Relational

26. You Don’t Like SQL The Death of Relational

27. You Don’t Like SQL The Death of Relational

28. You Don’t Like SQL The Death of Relational

29. So, Screw SQL
Good Riddance
The Death of Relational

30. Not Everyone Agrees
The Death of Relational

31. • Oh fuck those idiots. Reddit comment
• Developing the app for Google-sized scale is
a waste of your time, plus, there is no way
you will get it right. I Can't Wait For NoSQL to Die
• They reject relational databases and
substitute retro 1960s key-value stores from
the dark ages of practical computing... NoSQL is a Pile
of Crap
Not Everyone Agrees The Death of Relational

32. • In the case of the NoSQL hype, it isn’t generally
the inventors over-stating its relevance — most
of them are quite brilliant, pragmatic devs — but
instead it is loads and loads of terrible-at-SQL
developers who hope this movement invalidates
their weakness. Dennis Forbes, Getting Real about NoSQL and the SQL-Isn't-Scalable Lie
• Machines will get faster and cheaper all the
time, but you’ll still only have the same limited
programming resources that you had yesterday...
Mr. Moore gets to punt on sharding
Not Everyone Agrees The Death of Relational

33. Not Everyone Agrees The Death of Relational

34. More Than (My|No)SQL
The Death of Relational

35. “ There will never be a single system which
will maximize business value for every
possible usage pattern, so it pays to know
about a wide variety of architectures.
Coda Hale - Infrastructure Architect at Yammer
@coda
More Than (No|My)SQL The Death of Relational

36. More Than (No|My)SQL The Death of Relational

37. More Than (No|My)SQL The Death of Relational

38. More Than (No|My)SQL The Death of Relational

39. More Than (No|My)SQL The Death of Relational

40. More Than (No|My)SQL The Death of Relational

41. More Than (No|My)SQL The Death of Relational

42. More Than (No|My)SQL The Death of Relational

43. More Than (No|My)SQL The Death of Relational

44. More Than (No|My)SQL The Death of Relational

45. More Than (No|My)SQL The Death of Relational

46. More Than (No|My)SQL The Death of Relational

47. More Than (No|My)SQL The Death of Relational

48. The End
The Death of Relational