2 ms·
Working on a big microservice solution right now, it amazes me how inefficient we are: we are making HTTPL calls, replying HTTP calls, serializing data to JSON,
by DeathArrow 5y ago
Working on a big microservice solution right now, it amazes me how inefficient we are: we are making HTTPL calls, replying HTTP calls, serializing data to JSON, deserializing data from JSON in a long chain of calls.
I rather see a distributed application the same way as I see a monolithic application: I don't want to make HTTP calls, I don't want to serialize JSON, what I want is to call remote functions with my local data in a reliable, fast and efficient way. It seems weird that we can't just do that and instead we pack the data in layers upon layers, thus decreasing performance and increasing complexity a bit.
- coredog64 5y agoSame: At one point, we analyzed our app and determined that about half the assigned compute was being used for serializing and deserializing JSON. If the project wasn’t also years late they would have moved to Protobuf and saved millions.
- naasking 5y agoOr use Cap'n Proto [1] and eliminate all serialization costs. [1] https://capnproto.org/ https://capnproto.org/