Apache Thrift VS Protocol Buffers

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 / 2 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: about 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

> Aren’t a standard You mean like an IETF standard? That is true, although the specification is quite simple to implement. It is certainly a de-facto standard, even if it hasn’t been standardized by the IETF or IEEE or ANSI or ECMA. > inherently limits anything built on top of them to not be a standard either I’m not sure that strictly follows. https://datatracker.ietf.org/doc/html/rfc9232 for example directly... - Source: Hacker News / 4 months ago

The MQTT protocol is widely used in IoT applications because of its simplicity and ability to connect different data sources to applications using a publish/subscribe model. While many MQTT brokers support persistent sessions and can store message history as long as an MQTT client is not available, there may be cases where data needs to be stored for a longer period. In such cases, it is recommended to use a time... - Source: dev.to / 4 months ago

Generate a mock from an API definition Skyramp simplifies the process of mocking by allowing you to generate mocks directly from your API definitions, such as OpenAPI or Protobuf. This means you can easily create realistic mocks that mimic the behavior of your actual microservices. With the Skyramp CLI, it's as easy as running skyramp mocker generate ... With the relevant inputs. See the Skyramp Docs for which... - Source: dev.to / 5 months ago

Tsavo also touched upon how consistency is also crucial at the SDK level and the data layer. A fun fact about our company is that a majority of our client-side SDKs are generated off of protobuf specs or HTTP open API specs. This means that when a new endpoint with a certain capability is released, we can quickly have it available in Kotlin, TypeScript, Dart, Rust, Go, and some other languages. This rapid... - Source: dev.to / 5 months ago

This is a bit similar to roll your own crypto conversation. It is fun, and a great way to learn. And once done, you should do well to never deploy your own crypto in any real life application. Friends don't let friends roll their own protocol over UDP (or IP; I mean why not?). There are very few apps that have such an explicit requirements that they can't do away with TLS over any number of existing, and well... - Source: Hacker News / 6 months ago