LinkedIn Overhauls Log Storage
LinkedIn replaces its Kafka log storage with Northguard and Xinfra for improved scalability and operability to handle over 1.2 billion members.
4 min read
Visual TL;DR
over 1.2 billion members and exponential data volume increase
From the article 8 mentionsThis overhaul aims to address the exponential growth in data volume and complexity since Kafka was first implemented 15 years ago.
crucial for debugging and verification of data streams
From the article 7 mentionsData streams are fundamental to LinkedIn's thousands of services, enabling them to subscribe to and process information from other services.
metadata bottlenecks, cluster size, load balancing difficulties
From the article 6 mentionsLinkedIn is phasing out its long-standing Kafka infrastructure for a new homegrown system dubbed Northguard.
LinkedIn's new homegrown log storage system
From the article 7 mentionsNorthguard is engineered for high scalability and operability.
part of the new log storage infrastructure
From the article 4 mentionsTo ease the transition from Kafka, LinkedIn developed Xinfra, a virtualized Pub/Sub layer that sits above Northguard.
addressing challenges of the previous Kafka system
From the article 2 mentionsNorthguard is engineered for high scalability and operability.
handling 32 trillion records daily across 17 petabytes
From the article 2 mentionsThis abstraction layer maintains compatibility with existing applications while leveraging Northguard's improved scalability and operability.
© 2026 StartupHub.ai. All rights reserved. You may not republish this article in full without a license. Search engines and AI research tools may crawl and summarize for reference. Bulk reproduction or model training requires a license. See our terms.