While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 4 months ago

Services in general communicate via Thrift (and in some cases HTTP). Source: about 1 year ago

Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 1 year ago

RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago

Ts-rest is an open-source project, and it has a fast-growing community. You can check out their documentation here. - Source: dev.to / 2 months ago

Surprisingly, thanks to the power of TypeScript, new Node.js RPC frameworks like tRPC and ts-rest now provide extremely pleasant and snappy developer experiences. - Source: dev.to / 3 months ago

It is worth noting there are also options to get both compile time type safety and runtime validation using TypeScript. Personally I’m a fan of ts-rest: https://ts-rest.com/ Write a specification of your endpoints in TypeScript, and from that one spec you get: - Server side validation of requests/responses - A TypeScript API client - Auto-generated docs (OAS) - TypeScript types for requests and responses to use in... - Source: Hacker News / 8 months ago

Strong disagree. The barrier you presume is that OpenAPI specs are hard to write. Raw oAPI in yaml is indeed a pain, but there are good DSL's out there. I personally love Zod->OpenAPI, via https://ts-rest.com which uses https://www.npmjs.com/package/@anatine/zod-openapi. https://github.com/asteasolutions/zod-to-openapi is another alternative for Zod.... - Source: Hacker News / 8 months ago

I’ve recently been exploring https://ts-rest.com/ and it seems like a pretty solid project that can solve issues in my codebase. Source: 12 months ago