Why a Job Site Invented Kafka
How LinkedIn's tangle of point-to-point data pipelines led to Kafka's commit-log abstraction, and how one internal tool became industry infrastructure.
Category
6 articles
How LinkedIn's tangle of point-to-point data pipelines led to Kafka's commit-log abstraction, and how one internal tool became industry infrastructure.
Why LinkedIn built Venice to bridge offline-computed and streaming-computed data into a low-latency read-only serving store for machine learning features.
How LinkedIn built T-REX, its internal experimentation platform, to make running and trusting thousands of concurrent A/B tests routine rather than risky.
How LinkedIn's move to a service-oriented architecture forced a standardized REST framework, and why schema-driven API contracts paid off at scale.
Why LinkedIn built its own distributed document database to replace Oracle for online member data, and how it married timeline consistency with Kafka.
How LinkedIn built Apache Samza to pair with Kafka, using partitioned logs and local state to make stateful stream processing durable and rebalanceable.