How Netflix Scaled Its Real-Time Service Map
Automated news aggregation. Headlines and summaries are gathered from public feeds; see our editorial standards for sourcing, corrections, and AI-assist disclosure.
Netflix has described how it redesigned the streaming pipeline behind Service Topology, its real-time service dependencies map, to support production scale. The system uses three stages to separate intermediary resolution from enrichment and persistence, propagates backpressure to Kafka rather than dropping records, and uses server-sent events instead of gRPC for high-volume internal transfers. By Eran Stiller
Key takeaways
- 01Netflix has described how it redesigned the streaming pipeline behind Service Topology, its real-time service dependencies map, to support production scale.
- 02The system uses three stages to separate intermediary resolution from enrichment and persistence, propagates backpressure to Kafka rather than dropping records, and uses server-sent events instead of gRPC for high-volume internal transfers.
About this story
This story was aggregated from InfoQ. Headlines, summaries, and links are gathered automatically from public RSS feeds for your convenience.
Read the full story →For agents:JSON recordOpenAPIWebMCPllms.txt
