Ignite: Enabling multi-cloud and breaking vendor lock-in with Cloud Sidecar
summary
Live demo shows a Play/Scala front end and Python workers that originally talk to AWS S3 and SQS, then — with minimal code changes pointing endpoints to localhost ports 3450/3460 — Cloud Sidecar translates calls to Google Cloud Storage and Pub/Sub so images and messages move without changing app logic. It supports S3->GCS, SQS->Pub/Sub plus kinesis, dynamo, redshift mappings, does hot config reloads so no app restart is required, and the conversion visibly succeeds.
AI-written summary · about
chapters (5)
related talks
26mMulti-Cloud Native Data with Spring and VMware Data Solutions
28mOpening Keynote
58mService Mesh and Sidecars with Istio and Envoy
08mLightning Talk: Principles of Portability for Multi-Cloud Applications
01h 27mSpring Cloud at Netflix
35mConvergence of Serverless APIs & Compute
27mFrom Supercomputing to Serving: A Case Study Delivering Cloud Native Foundation Models
32mWhy Sidecars? Moving the Stack out of the Monolith
