Diego Runtime Overview
summary
Diego is a replacement container runtime built around a BBS (bulletin board store) that records desired work, an auctioneer that picks placements, cell-local rep + garden processes that create containers, and a converter that heals state. It runs LRPs (always-on, scalable app instances) and one-off tasks, supports buildpack and Docker images, and ties into CF via CC-bridge and route-emitter for HTTP, TCP and SSH routing. Current scale is 10k good, 50k adequate, target 250k+ while moving to a relational store.
AI-written summary · about
chapters (10)
- 0:00Introduction to Diego
- 1:53Core architecture overview
- 4:20Diego core components
- 7:06Workload types and abstractions
- 9:57Application execution details
- 13:05Scheduling and placement
- 17:45Coordination and high availability
- 20:36CC bridge and lifecycle management
- 23:03Routing and network integration
- 25:47Future directions and Q&A
related talks
37mCloud Foundry Diego Overview
32mImplementing the Schedulers: A Look at the Internals of Diego...
26mUnlocking Diego: Achieving Distributed Robustness Through Simplicity and Reliability
46mState or events? Which shall I keep?
14mBuilding High Availability and Scalability Online Computing Applications on Ray
44mUsing Mesosphere Enterprise DC/OS to Deliver Real-Time Microservices to a Global Fleet of Ships
26mData Processing on Ray
26mRay: A General Purpose Serverless Substrate?