The ABCs of Scaling MongoDB

901 views

Published on

Published in: Technology, Health & Medicine
1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

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

No notes for slide
  • \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
  • The ABCs of Scaling MongoDB

    1. 1. The ABCs ofSCALING MONGODB
    2. 2. @ethangunderson
    3. 3. Hiring
    4. 4. ChicagoDBNext Meeting 5/16 chicagodb.com
    5. 5. Questions?Comments?Shout Out!
    6. 6. “Stack Overflow Makes Slow Pages100x Faster By Simple SQL Tuning“
    7. 7. A is forscale After optimization
    8. 8. Any form of multiple node scalingcauses pain
    9. 9. Query Optimization
    10. 10. Slow query log
    11. 11. Restrict fields
    12. 12. Remove redundant indexes
    13. 13. Use covered indexes
    14. 14. More RAM!
    15. 15. The sad truth is, this will be enoughfor the majority of websites
    16. 16. B is forreplica sets are Bitchin’
    17. 17. WritesReads
    18. 18. Writes
    19. 19. Reads Writes
    20. 20. Reads Writes
    21. 21. Promoted to master
    22. 22. Writes/Reads
    23. 23. Comes back as a slave
    24. 24. C is forstrong Consistency throughauto sharding
    25. 25. Reads Writes
    26. 26. { ʻusernameʼ: ʻethanʼ, ʻageʼ: 23 }{ ʻusernameʼ: ʻbrianʼ, ʻageʼ: 70 }{ ʻusernameʼ: ʻmikeʼ, ʻageʼ: 26 }{ ʻusernameʼ: ʻdaveʼ, ʻageʼ: 40 }{ ʻusernameʼ: ʻzackʼ, ʻageʼ: 12 }
    27. 27. Reads / Writes[a - d] [i - m] [s-v][e - h] [n - r] [w-z]
    28. 28. Reads / Writes [a - d] [i - m] [s-v][e - h] [n - r] [w-z]
    29. 29. Reads / Writes [a - d] [s-v][e - h] [i - m] [w-z] [n - r]
    30. 30. Reads / Writes [i - m] [s-v][a - d] [n - r] [w-z] [e - h]
    31. 31. CAP
    32. 32. CAP
    33. 33. Thanks!

    ×