Mesomatic: The Cluster is a Library
summary
Mesomatic pairs Clojure with Apache Mesos to stop hand‑shuffling of machines by providing idiomatic types, scheduler and executor facets, a core.async facet that streams Mesos messages onto channels, and an allocate helper that plans collocation and instance counts. Example: a distributed cron runs two jobs (every 20 and 30 minutes, 0.5 CPU and 512 MB each) and converges the cluster to the desired topology using atoms, core.match and data diff. Claim: reduces ops work and keeps services on homogeneous hosts; it demonstrably launches, monitors and reconciles tasks. Mesomatic
AI-written summary · about
chapters (24)
- 0:00Start
- 0:43AIM OF THIS TALK
- 1:20OUTLINE
- 2:55FIRST SIGNS OF SUCCESS
- 3:45FEATURES GET ADDED
- 11:22MESOS MASTERS
- 12:48MESOS SCHEDULERS
- 13:11MESOS EXECUTORS
- 14:20OFFER BASED ALLOCATION MODEL
- 17:37WHY A LIBRARY
- 18:29COMPONENTS
- 19:22CLOJURE TYPES
- 19:53EXECUTOR AND SCHEDULER FACADES
- 20:45EXECUTOR FACADE: OUTPUT
- 21:38SCHEDULER FACADE: INPUT
- 22:57ANATOMY OF A RESOURCE OFFER
- 24:19CORE.ASYNC FACADES
- 25:36ALLOCATOR IMPLEMENTATION
- 26:12ADDITIONAL TASK FIELDS
- 30:42HANDLING TOPOLOGY CHANGES
- 31:14ATOM-BACKED CONFIGURATION
- 32:14MAKING CLEAR DECISIONS
- 35:49DID MESOS HELP?
- 36:35FUTURE WORK
related talks
59mBuilding Distributed Systems with Apache Mesos
41mEfficient cluster resource management by using Cook and Mesos
41mEfficient cluster resource management by using Cook and Mesos
23mHow cluster managers affect the landscape of modern distributed computing
27mKeynote Panel: Future of Cluster Management
46mWriting Stateful Frameworks
34mSimulating Our Apache Mesos Framework for Fun and Profit and...
33mDistributed Scheduler Hell