Strengths and Weaknesses of MongoDB
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Strengths and Weaknesses of MongoDB

on

  • 4,759 views

 

Statistics

Views

Total Views
4,759
Views on SlideShare
4,759
Embed Views
0

Actions

Likes
1
Downloads
58
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Strengths and Weaknesses of MongoDB Presentation Transcript

  • 1. MongoDB:Strengths & Weaknesses Presented by Luke Ehresman http://copperegg.com
  • 2. A.K.A.“Knowing when to usea hammer, and when to use a screwdriver.”
  • 3. Where did we come from?
  • 4. Where did we come from? The state of things a few years ago:
  • 5. Where did we come from? The state of things a few years ago: • Relational ruled
  • 6. Where did we come from? The state of things a few years ago: • Relational ruled • Normalize everything
  • 7. Where did we come from? The state of things a few years ago: • Relational ruled • Normalize everything • Shove it into a relational database
  • 8. Where did we come from? The state of things a few years ago: • Relational ruled • Normalize everything • Shove it into a relational database • The web grew, very large sites are common
  • 9. What is relational? Normalized data that relates to each other
  • 10. What is relational? Normalized data that relates to each other id name family_id id Family 1 Luke 1 1 Ehresman 2 Jetson 2 Fred 4 3 Smurf 3 George 2 4 Flintstone 4 Elroy 2 5 Papa 3
  • 11. What is relational? Normalized data that relates to each other id name family_id id Family 1 Luke 1 1 Ehresman 2 Jetson 2 Fred 4 3 Smurf 3 George 2 4 Flintstone 4 Elroy 2 5 Papa 3 Great for: • data reuse • data integrity • enforcing constraints • enforcing schema
  • 12. Example use cases
  • 13. Example use cases• Users with Accounts that have Transactions with Line Items
  • 14. Example use cases• Users with Accounts that have Transactions with Line Items• Person with Votes and Comments
  • 15. Example use cases• Users with Accounts that have Transactions with Line Items• Person with Votes and Comments• Blog with Articles and Users who Vote and leave Comments
  • 16. Relational DBs give you
  • 17. Relational DBs give you• Durability (guarantees that data is written)
  • 18. Relational DBs give you• Durability (guarantees that data is written)• Consistency (enforcing constraints)
  • 19. Relational DBs give you• Durability (guarantees that data is written)• Consistency (enforcing constraints)• Guarantees of atomicity
  • 20. Relational DBs give you• Durability (guarantees that data is written)• Consistency (enforcing constraints)• Guarantees of atomicity• Data portability (with modern SQL dbs)
  • 21. Relational DBs give you• Durability (guarantees that data is written)• Consistency (enforcing constraints)• Guarantees of atomicity• Data portability (with modern SQL dbs)• Slice and dice data, willy-nilly (SQL)
  • 22. Sometimes you just don’t care.
  • 23. Sometimes you just don’t care.
  • 24. Sometimes you just don’t care.• Sometimes speed is more important
  • 25. Sometimes you just don’t care.• Sometimes speed is more important• Sometimes data is highly segmented
  • 26. Sometimes you just don’t care.• Sometimes speed is more important• Sometimes data is highly segmented• Sometimes you can trust your app
  • 27. Sometimes you just don’t care.• Sometimes speed is more important• Sometimes data is highly segmented• Sometimes you can trust your app• Sometimes you know how data will be queried
  • 28. Sometimes you just don’t care.• Sometimes speed is more important• Sometimes data is highly segmented• Sometimes you can trust your app• Sometimes you know how data will be queried• Sometimes you don’t need everything that normalization and relational DBs give you
  • 29. Sometimes you just don’t care.• Sometimes speed is more important• Sometimes data is highly segmented• Sometimes you can trust your app• Sometimes you know how data will be queried• Sometimes you don’t need everything that normalization and relational DBs give you• Sometimes it’s not the end of the world if you lose some of your data
  • 30. Example use cases
  • 31. Example use cases• Blog with Comments (?? Really??)
  • 32. Example use cases• Blog with Comments (?? Really??)• Logging tons of data
  • 33. Example use cases• Blog with Comments (?? Really??)• Logging tons of data• Pre-processed data warehousing
  • 34. Enter: NoSQL
  • 35. Enter: NoSQL• These use cases are exactly why NoSQL databases have become popular
  • 36. Enter: NoSQL• These use cases are exactly why NoSQL databases have become popular• Perhaps too popular (but we’ll get to that)
  • 37. Enter: NoSQL• These use cases are exactly why NoSQL databases have become popular• Perhaps too popular (but we’ll get to that)• Store MASSIVE amounts of data
  • 38. Enter: NoSQL• These use cases are exactly why NoSQL databases have become popular• Perhaps too popular (but we’ll get to that)• Store MASSIVE amounts of data• Very (VERY) fast retrieval
  • 39. Enter: NoSQL• These use cases are exactly why NoSQL databases have become popular• Perhaps too popular (but we’ll get to that)• Store MASSIVE amounts of data• Very (VERY) fast retrieval• Usually better scalability than RDBMS
  • 40. Know Thyself (and thy data)
  • 41. Know Thyself (and thy data)
  • 42. Know Thyself (and thy data)• Why are you considering MongoDB?
  • 43. Know Thyself (and thy data)• Why are you considering MongoDB?• How will your data be queried?
  • 44. Know Thyself (and thy data)• Why are you considering MongoDB?• How will your data be queried?• How big do you need to scale?
  • 45. Know Thyself (and thy data)• Why are you considering MongoDB?• How will your data be queried?• How big do you need to scale?• Are you read-heavy, or write-heavy?
  • 46. Know Thyself (and thy data)
  • 47. Know Thyself (and thy data)• Read-heavy data
  • 48. Know Thyself (and thy data)• Read-heavy data • Slave reads?
  • 49. Know Thyself (and thy data)• Read-heavy data • Slave reads? • Size of data? Store it all in RAM?
  • 50. Know Thyself (and thy data)• Read-heavy data • Slave reads? • Size of data? Store it all in RAM? • Covered indexes for subset queries?
  • 51. Know Thyself (and thy data)• Read-heavy data • Slave reads? • Size of data? Store it all in RAM? • Covered indexes for subset queries? • How will you be querying?
  • 52. Know Thyself (and thy data)
  • 53. Know Thyself (and thy data)• Write-heavy data
  • 54. Know Thyself (and thy data)• Write-heavy data • Insert vs. update/upsert?
  • 55. Know Thyself (and thy data)• Write-heavy data • Insert vs. update/upsert? • Number of indexes?
  • 56. Know Thyself (and thy data)• Write-heavy data • Insert vs. update/upsert? • Number of indexes? • Cluster design (many small shards)?
  • 57. Know Thyself (and thy data)• Write-heavy data • Insert vs. update/upsert? • Number of indexes? • Cluster design (many small shards)? • Durability? Safe writes, or not? Journaling?
  • 58. Not all created equal
  • 59. Not all created equal• SQL (MySQL, Postgres, SQL Server, Oracle)
  • 60. Not all created equal• SQL (MySQL, Postgres, SQL Server, Oracle)• MongoDB, Riak, Cassandra, ...
  • 61. Not all created equal• SQL (MySQL, Postgres, SQL Server, Oracle)• MongoDB, Riak, Cassandra, ...• Key/Value (Redis, Tokyo Tyrant)
  • 62. SQL IS DEAD!
  • 63. far
  • 64.    fromSQL IS DEAD!
  • 65. far
  • 66.    fromSQL IS DEAD! NoSQL and MongoDB are great additions to your toolbox. Use as needed.