BestHub
Sign in
Tagged articles

Rest.li

3 articles · Page 1 of 1
Architecture Digest
Architecture Digest
Mar 22, 2016 · Backend Development

Evolution of LinkedIn’s Backend Architecture: From the Leo Monolith to a Scalable Service‑Oriented Platform

The article chronicles LinkedIn’s journey from a single‑server Leo monolith to a highly distributed, service‑oriented backend architecture, detailing the introduction of member graphs, read‑only replicas, caching layers, Kafka pipelines, Rest.li APIs, super‑blocks, and multi‑data‑center deployments to support billions of daily requests.

KafkaLinkedInRest.li
0 likes · 9 min read
Evolution of LinkedIn’s Backend Architecture: From the Leo Monolith to a Scalable Service‑Oriented Platform
21CTO
21CTO
Mar 20, 2016 · Backend Development

How LinkedIn Scaled to 350 Million Users: From Leo Monolith to 750+ Microservices

LinkedIn grew from a single monolithic Leo server handling all web requests to a complex ecosystem of over 750 independent services, employing graph databases, read replicas, caching layers, Kafka pipelines, Rest.li APIs, and multi‑data‑center deployments to support billions of daily queries.

Backend DevelopmentKafkaMicroservices
0 likes · 9 min read
How LinkedIn Scaled to 350 Million Users: From Leo Monolith to 750+ Microservices
21CTO
21CTO
Feb 6, 2016 · Backend Development

How LinkedIn Scaled to 300M Users: Lessons from a Decade of Backend Architecture

This article chronicles LinkedIn's evolution from a monolithic Leo application to a massive micro‑service ecosystem, detailing the introduction of member graphs, read‑only replicas, caching layers, Kafka pipelines, Rest.li APIs, super‑blocks, and multi‑data‑center strategies that enable handling billions of requests daily.

KafkaLinkedInMicroservices
0 likes · 8 min read
How LinkedIn Scaled to 300M Users: Lessons from a Decade of Backend Architecture