Launching the Next Generation Satellite Ground System on Cloud Foundry and Microservices
summary
DigitalGlobe replaces a brittle monolith with Cloud Foundry and microservices to support the WorldView-4 launch, running open-source CF for dev/test and PCF on OpenStack in production. The environment ingests ~5–6 TB raw/day (40–100 TB products), hosts ~800 services in dev but targets 60–80 microservices in production, uses Eureka, a Spring Config Server backed by Postgres, ELK logging, APIary and Software AG for API/registry, and a pipeline with isolated functional, integration and regression stages. Challenges: sprawl, multi‑foundation sync, SSL per developer and vendor licensing.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:24Cloud Foundry Summit - DigitalGlobe
- 1:01What does DigitalGlobe do?
- 2:141 Year of Collections
- 3:35Technical Decision Process
- 7:23Learn/Fix/Adapt Cycles
- 13:11Cloud Foundry DigitalGlobe
- 14:56Cloud Foundry Wins
- 17:21Cloud Foundry Challenges
- 19:36Cultural Challenges
- 20:33Future needs
- 21:21Delivery Pipeline
- 25:46CF Org Structure
- 27:05Contact Information
related talks
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
31mDeploying Microservice Architectures with Cloud Foundry
26mWriting Cloud Native Applications to Execute on Cloud Foundry
35mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
37mJava Microservices at Scale on Cloud Foundry, Today and Tomorrow
27mManaging the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini
51mMicroservices and Microfrontends: Scaling, Learning, Growing
01h 26mCloud Native Java with Spring Cloud Services