<story><title>LinkedIn adopts protocol buffers and reduces latency up to 60%</title><url>https://www.infoq.com/news/2023/07/linkedin-protocol-buffers-restli/</url></story><parent_chain><item><author>cbb330</author><text>Speaking as a current engineer at LinkedIn,&lt;p&gt;Big Tech companies will often conflate micro service with large distributed system.&lt;p&gt;These services are by no means at all micro.</text></item><item><author>iamflimflam1</author><text>&lt;i&gt;“50 thousand API endpoints exposed by microservices”&lt;/i&gt;&lt;p&gt;Feels that their problem may just be they went a bit too far on the microservices band wagon.</text></item></parent_chain><comment><author>jonathankoren</author><text>As a former LinkedIn engineer, let me ask, what happened? LI was using protobufs and BJSON like ten years ago. That was part of the whole conversion from Java serialization to rest APIs. This article implies that tossed everything, went back to text based JSON, and then said, “Well somabitch! Binary formats are faster than uncompressed text after all!”</text></comment>
<story><title>LinkedIn adopts protocol buffers and reduces latency up to 60%</title><url>https://www.infoq.com/news/2023/07/linkedin-protocol-buffers-restli/</url></story><parent_chain><item><author>cbb330</author><text>Speaking as a current engineer at LinkedIn,&lt;p&gt;Big Tech companies will often conflate micro service with large distributed system.&lt;p&gt;These services are by no means at all micro.</text></item><item><author>iamflimflam1</author><text>&lt;i&gt;“50 thousand API endpoints exposed by microservices”&lt;/i&gt;&lt;p&gt;Feels that their problem may just be they went a bit too far on the microservices band wagon.</text></item></parent_chain><comment><author>fnordpiglet</author><text>There are 19,000 LinkedIn employees world wide according to my cursory Kagi. That means more than two endpoints for every employee. I feel like regardless of micro or macro that’s an enormous sprawl of entropy.</text></comment>