Breaking vendor lock-in with Cloud Sidecar
summary
Cloud Sidecar claims to translate cloud APIs so existing apps can switch clouds with no code rewrites, deployed as a local sidecar that proxies and converts requests. The demo shows an image uploader moving from s3 to gcs and sqs to pubsub by reconfiguring Cloud Sidecar only, and the project is written in Go. It also emulates S3 multipart uploads for GCS, exposes a Postgres interface for Redshift→BigQuery, and is used in production at ActionIQ.
AI-written summary · about
chapters (8)
- 0:00Multi-cloud challenges
- 2:25Why multi-cloud matters
- 4:55Vendor lock-in problem
- 7:24Cloud Sidecar solution
- 10:51Live demo
- 14:20Cloud Sidecar features
- 22:23ActionIQ use case
- 25:10Try and contribute
related talks
32mWhy Sidecars? Moving the Stack out of the Monolith
38mThe Reality of Porting Kubernetes Apps Across Cloud Providers
27mOperationalizing Kubernetes Sidecars in Production at Salesforce
50mA hitchhicker's guide to Serverless computing
24mPower of Freedom & Flexibility: Going Cloud Agnostic
16mInfrastructure security, visibility and cost-optimization
27mProductionise any Application in Kubernetes Using Sidecar Containers
46mSpinnaker at Scale for Snap's Multi Cloud Service Mesh