10 years of evolution in the architecture of networked stateful applications
summary
A retrospective of a networking application platform’s architecture evolution from using L3fwd (no real stack) to a full software platform built on an event-driven architecture with a custom scheduler and TCP stack. Covers debugging capabilities and how this platform now underpins all the company’s products.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:12High-load network challenges
- 1:54Virtualization project start
- 3:00DPDK architecture
- 4:06RX/TX performance issues
- 5:07Queue bottlenecks
- 6:50Intel card limits
- 7:56L4 RX/TX optimization
- 9:25Multi-producer queue redesign
- 12:40Multi-producer queues
- 15:08New architecture gains
- 16:11Mesh topology challenges
- 17:58Scalability solutions
- 19:22Sending-side load balancing
- 20:28Evolution to L7 load balancer
- 22:37Flexible topology configs
- 24:25100Gbps card testing
- 25:56200Gbps results
- 27:02400Gbps plans
- 28:07Competitive advantages
- 28:27First deployment
- 29:09Q&A
related talks
07mApplication Networking is Broken - Platform Engineering to the...
03h 04mHow We Evolve Clever Cloud – Postmortem on a 10‑Year Project
26mKeynote: Make SDN Real
26mEvolution of Application Visibility for Telcos: From Programmable Switches to Cloud Native
26mF10: A Fault-Tolerant Engineered Network
32mPlatform Engineering for Software Developers and Architects (Redux)
41mHow to Build a Network Automation Stack From The Ground Up
50mEvolutionary Distillation of Architecture