LinkedIn Professional Network · View 02 of 30 · 1 · Context and scope
Decisions
- Every client call enters through one API layer; no client calls a mid-tier service directly
- A write lands in its system of record synchronously. Everything the write causes (fan-out, indexing, notifications, analytics) runs off the Kafka log
- Each discovery service has a documented degraded mode that the profile, feed and apply paths survive
Targets (p95)
- Profile read 200 ms · feed read 300 ms · post creation 300 ms · search 300 ms
- Message delivery 500 ms · notification creation 1 s
- 99.99% for identity, profile, feed, messaging and apply; 99.9% for search, recommendations and analytics
Deliberately omitted
- Stores: act 4 places every one of them
- Failure paths: views 26 (degradation) and 29 (privacy denials)
- Ads serving internals, which ride the feed but are a separate system