Mesos, Then and Now

on YouTube ↗45m

" summary

Apache Mesos begins as Berkeley’s Nexus in 2010 and becomes Twitter’s cluster fabric by 2012, paired with Aurora scheduler to run JVM services and improve packing across 64+ core hosts; early experiments use LXC and an internal bundler called app app, and Docker adoption is deliberately delayed so teams ship jars on host filesystems. Mesosphere commercializes Mesos; Twitter runs one Aurora instance per cluster, pushes for stateful frameworks, fixes scale bugs (master failover TCP floods) and pursues better resource isolation to raise utilization.

AI-written summary · about

" chapters (13)

1. 0:00Introduction and setup
2. 1:15Apache Mesos creators introduction
3. 3:19Early Mesos adoption at Twitter
4. 8:46Containers and Docker at Twitter
5. 12:38Why containers and Mesos
6. 19:01Aurora and Mesosphere's role
7. 22:35Mesos architecture explained
8. 27:17Two-level scheduling innovation
9. 30:05Who runs Mesos today
10. 34:58Resource utilization vs pipeline enablement
11. 38:30Twitter’s scale and innovation
12. 40:35Future of Mesos at Twitter
13. 43:51Collaboration and Q&A

" related talks

• 59mBuilding Distributed Systems with Apache MesosBen Hindman · Philly ETE 2015
• 42mMesos: The Operating System for your ClusterDavid Greenberg · Strange Loop 2014
• 57mA Distributed and Fault-Tolerant Application with Apache Mesos & Apache AuroraFlorian Pfeiffer · FrOSCon 2015
• 53mDocker as the Building Block for Datacenter-Scale ApplicationsBen Hindman · GOTO Amsterdam 2015
• 01h 00mDeveloping Distributed Systems with Apache MesosYaniv Rodenski · NDC Sydney 2016
• 22mKeynote: The Future of Apache Mesos and DC/OSYrieix Garnier · MesosCon Europe 2017
• 23mHow cluster managers affect the landscape of modern distributed computingAlex Rukletsov · Paris Container Day 2016
• 13mKeynote: Welcome and State of MesosBen Hindman · MesosCon Europe 2017