Innovation enabling - for Bosch eBikes
summary
Bosch eBike backend migrates from a private corporate cloud to AWS because private infrastructure hits scalability limits, creates knowledge silos and causes underutilization; a hybrid on‑transit data failed approach proves operationally painful with duplicated pipelines, tracing gaps and Jenkins confusion. Teams adopt Terraform and Lambda used for cloud‑agnostic infra-as-code, keep some services self‑managed (Elasticsearch/Grafana, Kubernetes+Istio), and standardize backups to avoid vendor-lock. Result: faster provisioning, cost accountability, easier hiring, large community support, and a working public‑cloud production deployment though hybrid complexity pushes the move.
AI-written summary · about
chapters (9)
- 0:00Bosch eBike cloud migration
- 1:50Bosch eBike ecosystem
- 4:41Private cloud limitations
- 8:32Public cloud transition
- 12:28Hybrid cloud failure
- 14:15Cloud agnostic strategy
- 18:15Changes after public cloud
- 20:07Choosing the right cloud
- 21:52Cloud decisions
related talks
01h 03mContinuous Security in the Cloud
27mData-driven and cloud-native ecosystems in the automotive industry
57mCreating value from confluence of technology forces (PRT250)
37mDriving efficiency and innovation at scale with cloud platforms
26mFull Life-Cycle Infrastructure Orchestration
38mAccelerating innovation through AWS Cloud technology
45mMercedes-Benz Aftersales: A cloud-first transformation
43mTransformation Path For Moving Applications Public Cloud