Cloud Foundry Networking: Enabling Direct Communication for Microservices - Chin, McClure
summary
Cloud Foundry adds a VXLAN overlay that gives each container a private IP and enables direct container-to-container traffic with lower latency; by default policies are deny and administrators create application-to-application rules enforced via tags and iptables. Integration with Spring Cloud Services/Eureka provides client-side discovery and load balancing (demo shows one front-end calling three back-end instances), with a network policy allowing front-end→back-end on port 8080; removing the policy causes failures and Hystrix circuit breakers to fall back. Feature ships on PWS and PCF 1.11+.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:32Overview
- 1:20Monolith
- 3:02Microservices
- 6:58Container to Container Networking
- 7:42How does this Networking stuff actually work?
- 10:07How Traffic Flows
- 12:21Bring your own service discovery
- 13:13SCS + Container Networking
- 19:51Policies!
- 26:22Resources
related talks
32mCF Networking: All Your Packets are Belong to Us
30mCF Networking: All Your Packets Belong to Us - Usha Ramachandran & Angela Chin, Pivotal
29mContainer Networking in Cloud Foundry
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
31mDeploying Microservice Architectures with Cloud Foundry
06mLightning Talk: Cloud Foundry Revisited: UDP, VoIP, and Beyond!
26mWriting Cloud Native Applications to Execute on Cloud Foundry
06mKeynote: Container to Container Networking for Cloud Foundry and Kubernetes