HTTP API In Action
summary
Mesos exposes three HTTP surfaces — scheduler, executor, operator APIs — that replace libmesos RPCs, enable language‑independent frameworks, and use POST subscription streams to deliver an event stream of JSON records. ArangoDB migrates parts of a 5k‑line C++ scheduler to a compact HTTP/SDK prototype (JavaScript SDK works for prototyping but is not production ready). Missing pieces: persistent framework state and persistent volumes for failover. Implementations must use persistent connections, handle heartbeats, and use SDKs for auth and robustness.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 8:29Goals
- 10:54Package
- 13:58Heartbeats
- 14:31Save
- 14:47Operator
- 17:01Versioning
- 18:33Frameworks
- 20:50Framework Overview
- 23:04Distributed Data Store
- 24:28Scheduling
- 25:41Resilient
- 26:38Framework
- 27:58Issues
- 29:20Improvements
- 30:13Less Code
- 32:14Warning
- 32:57Challenges
related talks
59mBuilding Distributed Systems with Apache Mesos
40mDistributed Data on Distributed Infrastructure
38mMesomatic: The Cluster is a Library
38mState is Hard: An SDK for Building Stateful Applications
42mStreaming Data Pipelines on Apache Mesos: Lessons Learned
22mAsynchronous Computing at Scale: Overview and Learning
32mNavigating Modern API Platforms: Insights & Strategies
46mState or events? Which shall I keep?