Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
MongoDB in the CloudJustin Smestad@jsmestadjustin@mongomachine.com                    Mongo Boulder                       ...
docs.mongomachine.com
Why host in the “Cloud”?
It makes MongoDB a commodity
Make scaling & deployment easy
The Platforms
Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
but don’t forget...it’s not all sunshine and rainbows
Headaches
Instance Selection
Headaches: Instance Selection  32-bit versus 64-bit  High Memory versus High CPU  Instance Location (even inside availabil...
Headaches: Instance Selection  32-bit versus 64-bit  High Memory versus High CPU  Instance Location (even inside availabil...
Headaches: Instance Selection  32-bit versus 64-bit  High Memory versus High CPU  Instance Location (even inside availabil...
Our SuggestionLargest instance you can afford to buy in pairs.*            * - that will meet your dataset requirements.
Disk Performance
Headaches: Disk Performance  Ephemeral versus Elastic Block Store (EBS)  EBS Performance  Choosing a RAID type (0, 1, or 5...
Headaches: Disk Performance  Ephemeral versus Elastic Block Store (EBS)  EBS Performance  Choosing a RAID type (0, 1, or 5...
Headaches: Disk Performance  Ephemeral versus Elastic Block Store (EBS)  EBS Performance  Choosing a RAID type (0, 1, or 5...
Headaches: Disk Performance  Ephemeral versus Elastic Block Store (EBS)  EBS Performance  Choosing a RAID type (0, 1, or 5...
Our SuggestionUse RAID-0 (if acceptable) and an EBS-basedAMI. Do not rely on EBS performance to beconstant.
Growth & Expansion
Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answ...
Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answ...
Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answ...
Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answ...
Our SuggestionUse mdadm with LVM for RAID to enhance IOperformance while keeping the ability to expand.This makes snapshot...
Disaster Recovery & Failover
Headaches: Disaster Recovery  Can feel a bit like “Yak Shaving”  To be good at it you will have to practice.  Knowing what...
Headaches: Disaster Recovery  Can feel a bit like “Yak Shaving”  To be good at it you will have to practice.  Knowing what...
Headaches: Disaster Recovery  Can feel a bit like “Yak Shaving”  To be good at it you will have to practice.  Knowing what...
Headaches: Disaster Recovery  Can feel a bit like “Yak Shaving”  To be good at it you will have to practice.  Knowing what...
Headaches: Disaster Recovery  EBS Reliability (better than physical, but not by much)  Snapshotting to S3 (expensive)  Rep...
Headaches: Disaster Recovery  EBS Reliability (better than physical, but not by much)  Snapshotting to S3 (expensive)  Rep...
Headaches: Disaster Recovery  EBS Reliability (better than physical, but not by much)  Snapshotting to S3 (expensive)  Rep...
Headaches: Disaster Recovery  EBS Reliability (better than physical, but not by much)  Snapshotting to S3 (expensive)  Rep...
Our Suggestion- Practice   recovery scenarios even the unlikely ones.- Replication  only gets you so far unless you go acr...
Why Mongo Machine?Moving On.
mongo   hosted MongoDB + data management www.mongomachine.com
Our Product
Managed SaaSWherever you need it.
mongo machine     hosted MongoDB + data managementManaged MongoDB Infrastructure   Our infrastructure on AWS or Rackspace ...
Management ConsoleAnalytics data about what your DB is doing.
Management ConsoleAnalytics data about what your DB is doing.
mongo machine     hosted MongoDB + data managementOur Goals    Increase developer efficiency    Be transparent with custom...
Questions?@jsmestad / @mongo_machinehttp://docs.mongomachine.com
Upcoming SlideShare
Loading in …5
×

MongoDB in the Cloud -- Mongo Boulder

3,111 views

Published on

Published in: Technology
  • Be the first to comment

MongoDB in the Cloud -- Mongo Boulder

  1. 1. MongoDB in the CloudJustin Smestad@jsmestadjustin@mongomachine.com Mongo Boulder Jan 21, 2011
  2. 2. docs.mongomachine.com
  3. 3. Why host in the “Cloud”?
  4. 4. It makes MongoDB a commodity
  5. 5. Make scaling & deployment easy
  6. 6. The Platforms
  7. 7. Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
  8. 8. Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
  9. 9. Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
  10. 10. Platforms: Amazon AWSThe Good Large RAM Sizes Community Paired Services (SQS, S3, etc) Reserved Instances
  11. 11. Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
  12. 12. Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
  13. 13. Platforms: Amazon AWSThe Not So Good Lack of small 64-bit instances IO Bottlenecks EBS Volumes
  14. 14. Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
  15. 15. Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
  16. 16. Platforms: RackspaceThe Good Internal Disk Raw Performance (CPU vs. ECPU) 64-bit instances
  17. 17. Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
  18. 18. Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
  19. 19. Platforms: RackspaceThe Not So Good Lack of large RAM instances * Community Lack of paired services
  20. 20. Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
  21. 21. Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
  22. 22. Platforms: TerremarkThe Good VMWare-based Fastest Cloud Option Fiber connected drives
  23. 23. Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
  24. 24. Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
  25. 25. Platforms: TerremarkThe Not So Good Lack of large RAM instances * Community Lack of paired services
  26. 26. but don’t forget...it’s not all sunshine and rainbows
  27. 27. Headaches
  28. 28. Instance Selection
  29. 29. Headaches: Instance Selection 32-bit versus 64-bit High Memory versus High CPU Instance Location (even inside availability zones)
  30. 30. Headaches: Instance Selection 32-bit versus 64-bit High Memory versus High CPU Instance Location (even inside availability zones)
  31. 31. Headaches: Instance Selection 32-bit versus 64-bit High Memory versus High CPU Instance Location (even inside availability zones)
  32. 32. Our SuggestionLargest instance you can afford to buy in pairs.* * - that will meet your dataset requirements.
  33. 33. Disk Performance
  34. 34. Headaches: Disk Performance Ephemeral versus Elastic Block Store (EBS) EBS Performance Choosing a RAID type (0, 1, or 5) Instance or EBS based AMI (machine images)
  35. 35. Headaches: Disk Performance Ephemeral versus Elastic Block Store (EBS) EBS Performance Choosing a RAID type (0, 1, or 5) Instance or EBS based AMI (machine images)
  36. 36. Headaches: Disk Performance Ephemeral versus Elastic Block Store (EBS) EBS Performance Choosing a RAID type (0, 1, or 5) Instance or EBS based AMI (machine images)
  37. 37. Headaches: Disk Performance Ephemeral versus Elastic Block Store (EBS) EBS Performance Choosing a RAID type (0, 1, or 5) Instance or EBS based AMI (machine images)
  38. 38. Our SuggestionUse RAID-0 (if acceptable) and an EBS-basedAMI. Do not rely on EBS performance to beconstant.
  39. 39. Growth & Expansion
  40. 40. Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answers, but also add complexity {fsync: 1, lock: 1} is important. Also don’t close the session!
  41. 41. Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answers, but also add complexity {fsync: 1, lock: 1} is important. Also don’t close the session!
  42. 42. Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answers, but also add complexity {fsync: 1, lock: 1} is important. Also don’t close the session!
  43. 43. Headaches: Growth/Expansion EBS Resizing (they must be detached) RAID 0 & RAID 1 can’t be resized LVM and XFS provide answers, but also add complexity {fsync: 1, lock: 1} is important. Also don’t close the session!
  44. 44. Our SuggestionUse mdadm with LVM for RAID to enhance IOperformance while keeping the ability to expand.This makes snapshotting volumes very hard.* * - alternative option is using RAID-5 but you will lose some performance.
  45. 45. Disaster Recovery & Failover
  46. 46. Headaches: Disaster Recovery Can feel a bit like “Yak Shaving” To be good at it you will have to practice. Knowing what can fail (ex: entire availability zones) ... this is going to take a few slides ...
  47. 47. Headaches: Disaster Recovery Can feel a bit like “Yak Shaving” To be good at it you will have to practice. Knowing what can fail (ex: entire availability zones) ... this is going to take a few slides ...
  48. 48. Headaches: Disaster Recovery Can feel a bit like “Yak Shaving” To be good at it you will have to practice. Knowing what can fail (ex: entire availability zones) ... this is going to take a few slides ...
  49. 49. Headaches: Disaster Recovery Can feel a bit like “Yak Shaving” To be good at it you will have to practice. Knowing what can fail (ex: entire availability zones) ... this is going to take a few slides ...
  50. 50. Headaches: Disaster Recovery EBS Reliability (better than physical, but not by much) Snapshotting to S3 (expensive) Replication Scenarios Connection Strings
  51. 51. Headaches: Disaster Recovery EBS Reliability (better than physical, but not by much) Snapshotting to S3 (expensive) Replication Scenarios Connection Strings
  52. 52. Headaches: Disaster Recovery EBS Reliability (better than physical, but not by much) Snapshotting to S3 (expensive) Replication Scenarios Connection Strings
  53. 53. Headaches: Disaster Recovery EBS Reliability (better than physical, but not by much) Snapshotting to S3 (expensive) Replication Scenarios Connection Strings
  54. 54. Our Suggestion- Practice recovery scenarios even the unlikely ones.- Replication only gets you so far unless you go across availability zones.- Calculate your “acceptable downtime” and base your infrastructure around that. If you want high availability & recovery, your better off paying someone else.
  55. 55. Why Mongo Machine?Moving On.
  56. 56. mongo hosted MongoDB + data management www.mongomachine.com
  57. 57. Our Product
  58. 58. Managed SaaSWherever you need it.
  59. 59. mongo machine hosted MongoDB + data managementManaged MongoDB Infrastructure Our infrastructure on AWS or Rackspace Management & Deployment to your own infrastructureManagement Console Instantly create new databases Track database trends Scale up & down on-demand
  60. 60. Management ConsoleAnalytics data about what your DB is doing.
  61. 61. Management ConsoleAnalytics data about what your DB is doing.
  62. 62. mongo machine hosted MongoDB + data managementOur Goals Increase developer efficiency Be transparent with customers Educate our clients
  63. 63. Questions?@jsmestad / @mongo_machinehttp://docs.mongomachine.com

×