In our MOU agreement with Amadeus, there are no requirements defined for how big of a topology, workload, or cluster size MongoDB's Cluster-to-Cluster solution must support. However, Amadeus expects that the Cluster-to-Cluster solution will work with any cluster they have in production. As a result, we hope to determine if our solution will scale to Amadeus' scale and workload. 

We have gathered the following information about Amadeus' clusters: 

• Summary of the ~40 (production) and ~70 (development) on-prem clusters
  • Amadeus Production Clusters
  • Amadeus Development Clusters
• Google Drive with a detailed audit on each cluster
  • Here is an example of a 9 shard 3.3TB cluster
  • Here is an example of a 12 shard 9.3TB cluster
• Workload 

  • The following list shows the maximum values for each metric over all mongods managed by Amadeus production Ops Manager (averaged to one data point per day): "OPCOUNTER_DELETE"  3880.894012685649
    
    "OPCOUNTER_INSERT" 547.351558876741
    "OPCOUNTER_UPDATE"  12035.873877845057
    "DOCUMENT_METRICS_INSERTED"   328.51541991846045
    "DOCUMENT_METRICS_DELETED" 166.70489563422413
    "DOCUMENT_METRICS_UPDATED" 5072.436333308759
    "OPLOG_RATE_GB_PER_HOUR"    51.537250799999995 
    
    
    Op counters are per second, and the oplog rate per hour is equal to 14.315903 MB per second