Cloud Migration do's and don'ts
summary
Outlines a three‑phase migration process (readiness assessment, technical planning, implementation) and insists on POCs, cost modeling and a roadmap; calls out concrete limits: 256 KB Lambda payload limit, default 1000 concurrent Lambda instances, and language cold starts like Java ~7.7s on Azure Functions. Recommends tooling: WAF, API Gateway, load balancers, GuardDuty/Sentinel, CosmosDB/DynamoDB choices for consistency, and hybrid examples (media on‑prem for cost). Stresses least‑privilege, encryption, monitoring, and that pay‑as‑you‑go can cost more if misconfigured.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:45Why migrate to cloud
- 3:12Migration challenges overview
- 6:01Mindset and metrics shift
- 8:08Security concerns
- 10:44Privacy and regulations
- 11:05Technical limitations
- 13:56Final advice and recommendations
- 14:40Q&A
related talks
46mEverything you need to know about cloud migration
29mJourney through the center of migrations
21mGround to Cloud: Your Migration Success Checklist
26mEffective Data Migration: Challenges & Success
32mDive into technical decisions from successful migrations
49mWhat to look out for when migrating your data to the cloud; is it REALLY the right choice?
44mMigrating Legacy Applications to the Cloud
52mMigrations: The opportunity for you and your customers