7 Comments

Some cool LinkedIn Lore is that Jay Kreps worked on implementing Kafka at LinkedIn, wrote a great blog post about it (https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying), and then went on to start Confluent, "the Kafka company".

Expand full comment

Nice history of LinkedIn. The original version was designed so that in order to link with someone you didn't know, you needed to find someone who you knew and who also knew the potential connection. Then you'd ask the person you knew for an introduction, and if the person agreed LI would connect you. That model didn't last long. (My internal LI user number is 1000.)

Expand full comment

What a journey! This must have been a wild ride for the engineers at LinkedIn. Thank you for the deep dive, engineering at such a huge scale is always interesting to read.

Expand full comment

Interesting read of how LinkedIn scaled from a monolithic architecture to SOA arch

Expand full comment

That is one roller coaster ride! An interesting case study to deep dive and learn about in separate parts.

Expand full comment

Thanks for the write up!

Did LI ever go into more details about the "super blocks"? I couldn't find anything beyond a blurb in their blog post and this newsletter.

We have a similar problem in my team, was curious if their experience could be helpful to us.

Expand full comment

Wonderful

Expand full comment