PREVIEW: Real-time Stream Processing at Scale
summary
New Relic describes switching to a streaming system built on Kafka to avoid a tenfold scaling nightmare, running 90 brokers across 600 topics and 4,000 partitions and ingesting about 15 million messages/sec. The team moves real-time monitoring events into Kafka as backbone and a datastore, replaces a timer-driven batch job that polled a custom-built database with continuous streams, publishes per-minute query outputs to Kafka topics for alerts and charts, and highlights inefficiencies of repeated historical queries and indexing bottlenecks.
AI-written summary · about
chapters (7)
related talks
30mEvent Streaming and the Future of Applications
47mBuilding High Performance Real-time Stream Processing Microservices
31mStreaming: Real-Time Architecture for Connected Products in Automotive
31mEvent Streaming on Rails
27mEvent Streaming Patterns for Ruby Services
05mGo for Real Time Streaming Architectures
36mStream All The Things!
01h 03mApache Kafka Event streaming platform for .NET developers
