Apache Thrift VS Registrator

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 / 3 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

Had the same problem recently, and was close to building a tool like yours. But I discovered Registrator. I added a small Consul instance and the consul provider configuration to traefik. Registrator ( https://github.com/gliderlabs/registrator ) automatically registers new docker services on the second maschine. Stopped services are automatically unregistered. Had to cross build Registrator for arm64, but this... Source: about 1 year ago