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
Diagram illustrating the Northguard data model with topics, ranges, and segments.
A look at how Northguard structures data for scalable log storage.· LinkedIn Engineering
Visual TL;DR
LinkedIn's GrowthDriver
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.
Data ReprocessingContext
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.
Kafka ChallengesDriver
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.
Introducing NorthguardCore
LinkedIn's new homegrown log storage system
From the article 7 mentionsNorthguard is engineered for high scalability and operability.
Xinfra LayerCore
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.
Enhanced OperabilityEffect
addressing challenges of the previous Kafka system
From the article 2 mentionsNorthguard is engineered for high scalability and operability.
Improved ScalabilityEffect
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.

LinkedIn is phasing out its long-standing Kafka infrastructure for a new homegrown system dubbed Northguard. This overhaul aims to address the exponential growth in data volume and complexity since Kafka was first implemented 15 years ago. The move is detailed in a recent LinkedIn Engineering post.

Data streams are fundamental to LinkedIn's thousands of services, enabling them to subscribe to and process information from other services. The ability to reprocess data is crucial for debugging and verification. Kafka, developed by LinkedIn a decade and a half ago, became the backbone for this ordered data pipeline, known as a log, supporting everything from user activity to AI features.

However, scaling Kafka to accommodate over 1.2 billion members has proven increasingly challenging. The platform now handles 32 trillion records daily across 17 petabytes, distributed across 10,000+ machines. Key issues included metadata and cluster size bottlenecks, load balancing difficulties, and compromises on consistency in favor of availability.

Introducing Northguard

Northguard is engineered for high scalability and operability. It shards data and metadata, minimizes global state, and employs a decentralized group membership protocol. Log striping is central to its design, ensuring even load distribution by breaking logs into smaller, replicated chunks called segments and ranges.

The system's data model consists of records, segments (sequences of records, serving as the unit of replication), ranges (contiguous key space segments), and topics (named collections of ranges). This structure allows for granular control and efficient replication.

Northguard's metadata is managed by vnodes, which are fault-tolerant replicated state machines utilizing Raft. A coordinator, the leader of a vnode, handles metadata operations and persists state, enabling seamless leader transitions. This metadata is sharded across vnodes using consistent hashing via a Dynamically-Sharded Replicated State Machine (DS-RSM) to prevent hotspots.

The Xinfra Layer

To ease the transition from Kafka, LinkedIn developed Xinfra, a virtualized Pub/Sub layer that sits above Northguard. This abstraction layer maintains compatibility with existing applications while leveraging Northguard's improved scalability and operability.

This evolution signifies LinkedIn's ongoing commitment to robust distributed systems log management, building on foundational technologies like Kafka to support its massive scale. The development of Northguard and Xinfra represents a significant step in ensuring the platform's future infrastructure can keep pace with its user growth and data demands, similar to how other platforms are innovating in distributed systems.

The adoption of Northguard and Xinfra underscores the critical role of scalable log storage systems in modern, data-intensive platforms, pushing the boundaries of what's possible in areas like AI development.

© 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.