--- title: How LinkedIn Reduced Latency with JSON | daily.dev description: LinkedIn switched from JSON to Protobuf to address performance issues in its microservices architecture. JSON, albeit human-readable and widely supported, led... canonical: https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How LinkedIn Reduced Latency with JSON | daily.dev og:description: LinkedIn switched from JSON to Protobuf to address performance issues in its microservices architecture. JSON, albeit human-readable and widely supported, led... og:url: https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3 og:image: https://api.daily.dev/og/posts/adtwqxIa3.png og:image:alt: How LinkedIn Reduced Latency with JSON og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How LinkedIn Reduced Latency with JSON **[Quastor Daily](https://daily.dev/sources/quastor)** · 9 min read · 78 upvotes · 0 comments ## Summary LinkedIn switched from JSON to Protobuf to address performance issues in its microservices architecture. JSON, albeit human-readable and widely supported, led to increased network bandwidth usage and higher serialization/deserialization latency. After evaluating several alternatives, LinkedIn chose Protobuf due to its smaller payloads, faster serialization/deserialization, type safety, and extensive language support. This switch resulted in improved throughput and up to 60% latency reduction for large payloads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#backend](https://daily.dev/tags/backend), [#microservices](https://daily.dev/tags/microservices) [View this post on daily.dev](https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How LinkedIn Reduced Latency with JSON","url":"https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3"},"datePublished":"2024-06-19T18:43:17.062Z","dateModified":"2024-10-05T18:48:45.216Z","description":"LinkedIn switched from JSON to Protobuf to address performance issues in its microservices architecture. JSON, albeit human-readable and widely supported, led...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ea641b9964ace0b95ca75c2db74cbc3a?_a=AQAEuiZ","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ea641b9964ace0b95ca75c2db74cbc3a?_a=AQAEuiZ","isAccessibleForFree":true,"articleSection":"Quastor Daily","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Quastor Daily","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/073e935e4893445ba562bf9e1ca38ec1","url":"https://daily.dev/sources/quastor"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-linkedin-reduced-latency-with-json-adtwqxia3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":78},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,microservices","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Quastor Daily","item":"https://daily.dev/sources/quastor"},{"@type":"ListItem","position":3,"name":"How LinkedIn Reduced Latency with JSON"}]} ```