It wasn't "great" mind you but it was "different" to what I was used too (https://servicemix.apache.org/) one interesting thing with this is that it's a monolith approach but each service was constructed as a loadable package. Source: about 1 year ago

Protocol Buffers: https://developers.google.com/protocol-buffers. - Source: dev.to / over 1 year ago

ProtocolBuffers’ OneOf message addresses the case of having a message with many fields where at most one field will be set at the same time. - Source: dev.to / over 1 year ago

That's definitely the bigger thing. I think something like Protocol Buffers (Protobuf) is what you're looking for there. Output the data and consume it by something that can handle the analysis. Source: over 1 year ago

These protocols prevent an O(N x M) explosion of code that have to solve for many cases. For example, since JSON is an almost ubiquitous format for wire transfer (although other things do exist like protobufs), if I had N data formats that I want to serialize, I only need to write N serializers/deserializers (SerDes). If there was no such narrow waist and there were M alternatives to JSON in wide usage, I would... Source: over 1 year ago

gRPC uses protocol buffers (it is an open source message format) as the default method of communication between client and server. Also, gRPC uses HTTP/ 2 as the default protocol. - Source: dev.to / over 1 year ago