The Cloud Foundry Bits-Service Myth Buster!
summary
Extracts bits handling from the Cloud Foundry controller into a separate bits-service microservice that currently implements all verbs for five resources (droplets, packages, buildpacks, app cache, buildpack cache), proxies local disk plus two object stores (S3 and OpenStack Swift) via the fog adapters, and runs CI pipes testing against three real storage backends. It moves long uploads out of the controller thread pool, allowing independent scaling and faster CF push times; implemented in Ruby/nginx now with a planned reimplementation in Go for better performance.
AI-written summary · about
chapters (11)
- 0:00The Bits-Service Myth Buster
- 0:25Agenda
- 1:11What is the Bits-Service?
- 2:34Example: cf push --no-start
- 8:08Where does Cloud Foundry store bits ?
- 10:54Why do we need a Bits-Service ?
- 16:10How will the Bits-Service change interaction?
- 18:04Challenges we faced
- 21:59What did we learn ?
- 24:53How does it affect you? How does it help you?
- 27:15Future Plans
related talks
22mWhat is the Bits-Service?
31mDeploying Microservice Architectures with Cloud Foundry
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
24mCloud Foundry Cookbook
27mDistributed Service Bundles for Cloud Foundry - Krishanu Biswas, SAP
34mSplit That Monolith: a Java on Cloud Foundry Story
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
26mWriting Cloud Native Applications to Execute on Cloud Foundry