Efficient Navigation for Modern Networks
summary
128 Technology builds a session‑based routing system that keeps per‑flow state and routes by service identity rather than IP topology, claiming faster reconvergence and no encapsulation headers. A custom protocol called Service Topology Exchange (STEP) pushes JSON service/topology files into an in‑memory DB diffs registry (GitHub‑like push/diff model), letting routers pick paths by measured delay/jitter and load. Deployed with customers across US, Europe and Japan, the company is ~1.5 years old with ~100 staff and reports lower overhead, realtime visualization and predictable path selection.
AI-written summary · about
chapters (6)
related talks
19mStarfish: A Topology-Routing Co-Design for Small-Scale Data Centers
20mContra: A Programmable System for Performance aware Routing
16mFoundations of Routing & Switching: Scalable Network Infra
21mThe Evolution of Traffic Routing in a Streaming World
48mRethinking Connectivity
21mSemi-Oblivious Traffic Engineering: The Road Not Taken
16mExpress Lane to Efficiency and Reliability: Multi-Dimensional Control in Meta’s Express..
33mCheap Routes, Fast Paths & Keeping Track
