Hacker News Reader

From rest.li's github page[0] -

At LinkedIn, we are focusing our efforts on advanced automation to enable a seamless, LinkedIn-wide migration from Rest.li to gRPC. gRPC will offer better performance, support for more programming languages, streaming, and a robust open source community. There is no active development at LinkedIn on new features for Rest.li. The repository will also be deprecated soon once we have migrated services to use gRPC. Refer to this blog[1] for more details on why we are moving to gRPC.

[0] - https://github.com/linkedin/rest.li

[1] - https://engineering.linkedin.com/blog/2023/linkedin-integrat...

from the article:

> Based on the learnings from the Protocol Buffers rollout, the team is planning to follow up with migration from Rest.li to gRPC, which also uses Protocol Buffers but additionally supports streaming and has a large community behind it.

Yep, REST make no sense between microservices, for what are basically RPCs.

How is gRPC related? You send JSON or Protobuf over gRPC

No Swift support.

https://github.com/grpc/grpc-swift

Thanks. It's not in their list of supported languages: https://grpc.io/docs/languages/