New Requirements for Application Delivery in a Micro-services Application World
summary
Argues that microservices force the network to become software-defined and composed of data-driven network functions, with management shifting from tens (10–15) to thousands or 100,000 instances and requiring centralized state, analytics and HA. Calls for crypto micro‑segmentation, client‑directed load balancing, service discovery instead of IPAM, and different handling of north‑south versus east‑west traffic. Announces Netscaler CPX Express, a fully featured containerized Netscaler build, released free for microservices use, and recommends RESTful APIs to lower the networking skills barrier.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:31Netscaler and proxy history
- 5:19Networking for microservices
- 7:26Management and state challenges
- 10:55Enterprise bridge strategies
- 14:13Announcing Netscaler CPX
- 15:47Q&A on developer engagement
related talks
48mChallenges in Implementing MicroServices
23mMicroservices Architectures: Agility vs Complexity
25mMaking microservices a behaviour not a buzzword
37mKnee Deep in Microservices
54mThe Long Sad History of Microservices
49mChallenges in Implementing Microservices
50mMicroservices Design Patterns for Java Application
26mPros/Cons of Microservices