UpdatePDX & Tim Anglade present  Failures,  Conjectures& Closure
Prologue( A converted warehouse, somewhere near the banks ofthe Willamette. The year is two thousand and eleven.)         ...
Act IFailing
( Bradford Stephens enters, stage right )
( Sarah Novotny enters, stage right )
( Alex Payne enters, stage right )
( Tim Anglade enters, stage right )
Act IIMaking Sense
data Hosting & AnalYTICS  Your CLOUD OR MINE
Should I use <…> ?It sounds incredibly     appealing!
Let me tell you abouta trend-setting, industry-leading      technological revolution   I’m very passionate about…
155856_Zamboni_Flyer.qxd:ZAMBONI 525 INSERT FINAL   5/26/10   2:11 PM   Page 1
Electronic ControlsThe Ultimate Machine
Actual Volume      2.83 m3 (100 cu. ft.)Compacted          3.54 m3 (125 cu. ft.)Excess Water       416 L (110 USG, 92 IMP)...
Should I use <…> ?Answer: it depends
Rules of Thumb
MongoDB is great, amongst other things, for…prototyping.
CouchDB is great, for example…if your queries don’tchange and you stay at a“small” scale.
BigCouch & Riak are great, amongst other things…when you valuedistribution & persistenceabove all else.
Hadoop is great, amongst other things, for…overnight analytics.
Redis is great, amongst other things, as…a data glue betweenmultiple parts of your app(queues, caches, etc.].
Cassandra is great, amongst other things, as…a starting point to build& extend on.
Neo4J is great, for example, if…you’d otherwise have todo a lot of self-joins.
A modest proposalSeven NOSQL Propositions
Proposition 1[the cardinal]Only use NOSQL if you have to.
Corollary 1.aIf you ask for NOSQL by name,you probably don’t need it.
[aside]Never forget the operationalcomplexity.
Proposition 2[the eternal]Some things will always be betterachieved with an RDBMS
Proposition 3(the modified Moon methodology)Distribution Modelvs. Data Modelvs. Disk Data Structure.
“If you have a ton of data then you must use one of thedistributed datastores and your requirements for howyou want to que...
Proposition 4[the nemesis]Catchy phrases are red herrings.
“Use the right toolfor the right job.”
“Polyglot persistence.”
Proposition 5[the brute]Hardware will always help;but it will never save you.
Proposition 6[the Black conjecture]Given enough time, mostNOSQL projects gravitatetowards a MapReduce-like modelfor comput...
Proposition 7[the paranoïd ]Trust no one.That goes double if they talkabout CAP.
Act IIIBuilding
Failures, Conjectures & Closure
Failures, Conjectures & Closure
Failures, Conjectures & Closure
Failures, Conjectures & Closure
Upcoming SlideShare
Loading in...5
×

Failures, Conjectures & Closure

719
-1

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
719
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Failures, Conjectures & Closure

  1. 1. UpdatePDX & Tim Anglade present Failures, Conjectures& Closure
  2. 2. Prologue( A converted warehouse, somewhere near the banks ofthe Willamette. The year is two thousand and eleven.) ( Tim Anglade enters, stage left )
  3. 3. Act IFailing
  4. 4. ( Bradford Stephens enters, stage right )
  5. 5. ( Sarah Novotny enters, stage right )
  6. 6. ( Alex Payne enters, stage right )
  7. 7. ( Tim Anglade enters, stage right )
  8. 8. Act IIMaking Sense
  9. 9. data Hosting & AnalYTICS Your CLOUD OR MINE
  10. 10. Should I use <…> ?It sounds incredibly appealing!
  11. 11. Let me tell you abouta trend-setting, industry-leading technological revolution I’m very passionate about…
  12. 12. 155856_Zamboni_Flyer.qxd:ZAMBONI 525 INSERT FINAL 5/26/10 2:11 PM Page 1
  13. 13. Electronic ControlsThe Ultimate Machine
  14. 14. Actual Volume 2.83 m3 (100 cu. ft.)Compacted 3.54 m3 (125 cu. ft.)Excess Water 416 L (110 USG, 92 IMP)Ice Making 738 L (195 USG, 162 IMP)Wash Water 310 L ( 82 USG, 68 IMP)Total 1048 L (277 USG, 230 IMP) 95 L ( 25 USG, 21 IMP)Horizontal Auger 25.4 cm ( 10 in.) dia. 81.25Vertical Auger 25.4 cm ( 10 in.) dia. (77 in. Blade)Snow Tank Down 4.04 m ( 159 in.)Snow Tank Up 5.03 m ( 198 in.)Snow Tank Down 2.26 m ( 89 in.) 89Snow Tank Up 3.91 m ( 154 in.) 77 in. Blade 2.06 m (81.25 in.) 86 in. Blade 2.30 m (90.25 in.) 1.95 m ( 77 in.) (7 7 in 1.37 m ( 54 in.) .B la de ) 77 in. Blade 4.86 m (16.0 ft.)At Conditioner 86 in. Blade 5.00 m (16 ft. 4.5 in.)77 in. Blade 1.27 x 12.7 x 195.6 cm ! in. x 5 in. x 77 in.86 in. Blade 1.27 x 12.7 x 218.4 cm ! in. x 5 in. x 86 in. with 86 in. Conditioner
  15. 15. Should I use <…> ?Answer: it depends
  16. 16. Rules of Thumb
  17. 17. MongoDB is great, amongst other things, for…prototyping.
  18. 18. CouchDB is great, for example…if your queries don’tchange and you stay at a“small” scale.
  19. 19. BigCouch & Riak are great, amongst other things…when you valuedistribution & persistenceabove all else.
  20. 20. Hadoop is great, amongst other things, for…overnight analytics.
  21. 21. Redis is great, amongst other things, as…a data glue betweenmultiple parts of your app(queues, caches, etc.].
  22. 22. Cassandra is great, amongst other things, as…a starting point to build& extend on.
  23. 23. Neo4J is great, for example, if…you’d otherwise have todo a lot of self-joins.
  24. 24. A modest proposalSeven NOSQL Propositions
  25. 25. Proposition 1[the cardinal]Only use NOSQL if you have to.
  26. 26. Corollary 1.aIf you ask for NOSQL by name,you probably don’t need it.
  27. 27. [aside]Never forget the operationalcomplexity.
  28. 28. Proposition 2[the eternal]Some things will always be betterachieved with an RDBMS
  29. 29. Proposition 3(the modified Moon methodology)Distribution Modelvs. Data Modelvs. Disk Data Structure.
  30. 30. “If you have a ton of data then you must use one of thedistributed datastores and your requirements for howyou want to query that data will most likely drive thechoice of which database to use.If, however, you do not have a ton of data then thechoice basically comes down to personal preference.”
  31. 31. Proposition 4[the nemesis]Catchy phrases are red herrings.
  32. 32. “Use the right toolfor the right job.”
  33. 33. “Polyglot persistence.”
  34. 34. Proposition 5[the brute]Hardware will always help;but it will never save you.
  35. 35. Proposition 6[the Black conjecture]Given enough time, mostNOSQL projects gravitatetowards a MapReduce-like modelfor computations.
  36. 36. Proposition 7[the paranoïd ]Trust no one.That goes double if they talkabout CAP.
  37. 37. Act IIIBuilding
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×