Origins of NoSQL movement, description of approaches and different trade-offs new databases make

1. SQL or NoSQL, that is the question! October 2011 Andraž Tori, CTO at Zemanta @andraz andraz@zemanta.com

6. So this is the end, right?

7. Why the heck would someone not want SQL?

9. Some other perspectives...

10. Let's say ...

11. You are a big tech company, located on west coast of USA

15. You are...

18. Numbers everybody should know! Jeff Dean at famous Stanford talk L1 cache reference 0.5 ns Branch mispredict 5 ns L2 cache reference 7 ns Mutex lock/unlock 25 ns Main memory reference 100 ns Compress 1K bytes w/ cheap algorithm 3,000 ns Send 2K bytes over 1 Gbps network 20,000 ns Read 1 MB sequentially from memory 250,000 ns Round trip within same datacenter 500,000 ns Disk seek 10,000,000 ns Read 1 MB sequentially from disk 20,000,000 ns Send packet CA->Netherlands->CA 150,000,000 ns

21. So smart guys create solutions to these internal challenges

24. Solving problems of big guys?

25. Total Sites Across All Domains August 1995 - October 2011, NetCraft

26. Yesterday's problem of biggest guys Is today's problem of garden variety startup

28. And so we end up with Cambrian explosion

31. These solutions don't have much in common, Except...

32. They definitely aren't SQL

33. Not Only SQL

34. So what are these beasts?

37. At the core, it's a different set of trade-offs and operational constraints

40. A consistent topic: CAP Theorem

42. "There is no free lunch with distributed data” – HP

44. But this is horrible!

45. … you already are eventually consistent! :) If your database stores how many vases you have in your shop...

48. There's not even a proper taxonomy of features different NoSQL solutions offer

49. And this presentation is too short to present whole breadth of possibilities

62. Not enough time to go into data model...

80. Hive

85. General notes

89. And if you don't take anything else from this presentation...

93. But there's more to it