Platform Engineering's Hidden Network Challenge
summary
Claim: major cloud providers do not support multicast natively, and five concrete barriers explain why—state explosion in SDN control planes, multi‑tenancy data‑leak risk, operational churn, virtualized performance hit, architectural mismatch with microservices. Practical fixes tested are specific: overlay with GRE tunnels to a marketplace router and central PIM/BGP, or push functionality into the app or use Amazon SQS Cloud Pub/Sub or CDN. Each workaround raises measurable costs, monitoring gaps, and migration complexity.
AI-written summary · about
chapters (8)
- 0:00Introduction to the Topic
- 0:37Understanding Multicast
- 2:35Challenges of Implementing Multicast in Cloud
- 5:36Impact on Infrastructure Automation
- 8:14Alternative Approaches to Multicast
- 11:24Challenges with Alternative Approaches
- 13:52Future Prospects and Emerging Technologies
- 15:59Conclusion
related talks
37mPanel Discussion: Cloud Native Networking State of the Union
32mService Networking Within Air-Gapped Environments: Deployment Strategies and Operat...
31mBreaking the Single-Network Barrier: A Cross-Domain Look at…
40mNoverlay Networks for Health and Wellbeing
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
27mBuilding an Edge Computing Platform for Network Services Using Cloud Native Technology [I]
23mBYO Infrastructure: Who needs to run a control plane, anyway?
31mReverse Engineering Cloud Native: Interoperability and Community