4. ways of running on Mesos
• 3 ways, while every coin has two sides
✓ develop scheduler running on Mesos
✓ components containerized(options) +
marathon
✓ batch restful api
8. PaaS
• Platform as a Service
• You can focus on your application, not the
infrastructure
• We can focus on making the platform resilient
and self-healing
10. Marathon
• PaaS on Mesos
• init.d for the cluster
• Docker support
• Scales at the click of a button
• roll-back
• Blue-Green Deployment
• RESTful API
• Manages edge routes -
HAproxy
11. Marathon
• health check, instead of supervisord
• constraints
• resources
• force pull image
• zookeeper is the bottleneck
• docker images warm-up or dfs
13. docker
• docker build image
• base image + wget executable program: run-
time
• tag image by code release version
• exited containers GC
14. Service Discovery
• Mesos-DNS(actively developing)
• one mesos-dns one slave
• stateless, replica
• RESTful API
• HAproxy/Bamboo
• 1 container 1 IP
• IPAM
• mesos container, instead docker container
• docker-Weave integration
• network isolation IS NOT Service Discovery
• host or bridge
• performance vs security
15. Load Balance
• Mesos-DNS
• round robin
• dynamic load
• HAproxy/Bamboo
• ip/source hash
• round robin
• least conn
• dynamic load