Your SlideShare is downloading. ×
NoSQL isn't NO SQL
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

NoSQL isn't NO SQL

2,146
views

Published on

Matthew McCullough's and Tim Berglund's presentation on a survey of NoSQL tools to the Denver Open Source Users Group

Matthew McCullough's and Tim Berglund's presentation on a survey of NoSQL tools to the Denver Open Source Users Group

Published in: Education

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,146
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Why NoSQL isn’t NO SQL by Tim Berglund and Matthew McCullough
  • 2. Data Scale
  • 3. Gigabyte
  • 4. Terabyte
  • 5. Petabyte
  • 6. 10s of Petabytes
  • 7. Transaction Volume
  • 8. Pedestrian data volumes
  • 9. Just be lazy
  • 10. Wait for a faster CPU!
  • 11. Wait for a faster hard drive!
  • 12. Wait for faster RAM!
  • 13. Can’t be lazy anymore
  • 14. More reads, less writes
  • 15. More writes, less reads
  • 16. Eventually consistent
  • 17. ACID
  • 18. The lies SQL tells you...
  • 19. Memory is good
  • 20. Precomputation is good
  • 21. Normalization is good
  • 22. Duplicating data is bad
  • 23. CAP Theorem
  • 24. 2000, Eric Brewer
  • 25. MIT CS
  • 26. Want three...
  • 27. Consistency Availability Partition tolerance
  • 28. Can have two...
  • 29. Proven to be the case
  • 30. NoSQL Personalities
  • 31. Structured
  • 32. Semi-structure
  • 33. Unstructured
  • 34. The Players
  • 35. Column Oriented Store
  • 36. Key Value Store
  • 37. Document Database
  • 38. Not Only SQL
  • 39. Re-examine requirements
  • 40. Which piece needs to be fast?
  • 41. What part needs to be highly available?
  • 42. Which part needs extreme scalability?
  • 43. Life as an architect is getting harder
  • 44. Now you’re responsible for knowing about and making tradeoffs
  • 45. Lets you say Petabyte
  • 46. And that makes you cool
  • 47. Thanks for listening
  • 48. http://delicious.com/matthew.mccullough/nosql
  • 49. • http://blog.nahurst.com/visual-guide-to- nosql-systems • http://nosql.mypopescu.com/ • http://delicious.com/matthew.mccullough/ nosql • http://refcardz.dzone.com/refcardz/getting- started-nosql-and-data