Comcast: Private-Cloud Self-Service MongoDB at Scale 200 Application Arch - Jayson Hurd & Jay Runkel

June 29, 2017

Jay Runkel, Principal Solution Architect, MongoDB & Jayson Hurd, Comcast

When architecting a MongoDB application, one of the most difficult questions to answer is how much hardware (number of shards, number of replicas, and server specifications) am I going to need for an application. Similarly, when deploying in the cloud, how do you estimate your monthly AWS, Azure, or GCP costs given a description of a new application? While there isn't a precise formula for mapping application features (e.g., document structure, schema, query volumes) into servers, there are various strategies you can use to estimate the MongoDB cluster sizing. This presentation will cover the questions you need to ask and describe how to use this information to estimate the required cluster size or cloud deployment cost.

 

Previous Video
Building a Microservices-based ERP System using Node.js and MongoDB - Jerry Reghunadh
Building a Microservices-based ERP System using Node.js and MongoDB - Jerry Reghunadh

Next Video
eBay: Practical Design Patterns for Building Applications Resilient to Infrastructure Failure - Feng Qu
eBay: Practical Design Patterns for Building Applications Resilient to Infrastructure Failure - Feng Qu