Mark ramm To relate or not to relate

878 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
878
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Hippie/Bad Trip\nAtomic\nConsistent\nIsolated\nDurable\n\n\n
  • \n
  • There are ways to solve all these problems.\n
  • There are ways to solve all these problems.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Consistency == Atomic + isolated\nAvailability == uptime\nPartition Tolerance == shardable? \n
  • \n
  • \n
  • \n
  • * basically available, \n* soft state,\n* eventually consistent\n
  • \n
  • Fossforus, Consume, Dstats, etc\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Mark ramm To relate or not to relate

    1. 1. relate or !relate mark ramm
    2. 2. Tools Matter
    3. 3. Data mattersjust as much
    4. 4. robust scalable simple flexible DSL a good mix consistant Topic SQLavailable ACID CAP Tools Matter Knowpartition Your mongodbtolerant NoSQL Tools Screws and Nails scalable siding focused simple deck fast Topic flexible
    5. 5. ToolsMatter Know Your mongodb Tools Screws and Nails siding deck
    6. 6. robust scalable simpleflexible DSL a good mix well known SQL ACID Tools Matter
    7. 7. ACIDhttp://www.flickr.com/photos/di4b0liko/2292648884/
    8. 8. Blah, blah blah, you arenot normal enough
    9. 9. Why I NEED Relational• I can’t use NoSQL because... • It’s financial data (need consistency) • My data is relational
    10. 10. Why I NEED Relational• I can’t use NoSQL because... • It’s financial data (need consistency) • My data is relational
    11. 11. Why I NEED Relational I T S H• I can’t use NoSQL because... L • It’s financial data L (need consistency) • My data is relational U B
    12. 12. But...
    13. 13. robust scalable simpleflexible DSL a good mix well known SQL ACID Tools Matter
    14. 14. Blah, blah blah, you aretoo normal
    15. 15. So why Use RDBS• DSL for ad-hock queries• blah blah inconsistencies blah blah latency
    16. 16. blah, blah,blah, blah, blah
    17. 17. taxonomy of NoSQL• key/value store• distributed key/value stores• column oriented stores• map-reduce store/system• document oriented store• graph oriented stores
    18. 18. NoSQL
    19. 19. NoSQL
    20. 20. consistantavailable CAP Toolspartition Mattertolerant NoSQL scalable focused simple fast Topic flexible
    21. 21. CAPhttp://www.cs.berkeley.edu/~brewer/cs262b-2004/PODC-keynote.pdf
    22. 22. consistantavailable CAP Toolspartition Mattertolerant NoSQL scalable focused simple fast Topic flexible
    23. 23. It’s“WebScale”
    24. 24. It’s“WebScale”
    25. 25. I T It’s H S L“WebScale” L U B
    26. 26. http://www.flickr.com/photos/beigephotos/900974545/
    27. 27. taxonomy of NoSQL• key/value store• distributed key/value stores• column oriented stores• map-reduce store/system• document oriented store• graph oriented stores
    28. 28. ToolsMatter Know Your mongodb Tools Screws and Nails siding deck
    29. 29. directory directory directory Mongo Slave Mongo Slave Mongo Slave fetcher sf.gobble Mongo Master fetcher feed apissf.net freshmeat.net hosted apps etc
    30. 30. merciless.sourceforge.net
    31. 31. MongoDB has a query languageselect * from document where x=3and y="foo"db.things.find( { x : 3, y : "foo" } );
    32. 32. Conditional Updatesdb.people.update( { name:"Joe" },{ $inc: { x:1, y:1 } }, true
    33. 33. blah, blah,blah, blah, blah
    34. 34. ConcludingUnscientificPostscript
    35. 35. •F i g u r e o u t w h a t YOUR app needs
    36. 36. •F i g u r e o u t w h a t YOUR app needs•D o n ’ t o b s e s s a b o u t SCALE you’ll never achieve
    37. 37. •F i g u r e o u t w h a t YOUR app needs•D o n ’ t o b s e s s a b o u t SCALE you’ll never achieve•U s e t h e r i g h t t o o l f o r the job

    ×