3 ms·
I'm curious--what sort of workload are you looking at where JSON/HTTP is insufficient? We do a lot of realtime signal streaming, and haven't had many problems.
by angersock 12y ago
I'm curious--what sort of workload are you looking at where JSON/HTTP is insufficient?
We do a lot of realtime signal streaming, and haven't had many problems. We'll be switching to a different format (or embedded format) to better handle some numerical pickiness on our end, but the fundamental transport is fine.
- XorNot 12y agoI think 'streaming' is the operative difference there. If you're opening a connection and sending large amounts of JSON 1-way then header/encoding overhead is basically not a problem. But a 2-way RPC protocol is basically making a separate HTTP request each time. For log file messages you're going to be sending more header more object definitions and headers than data. I'm curious how you're formatting your JSON too - some formats are going to be way lighter then others.
- angersock 12y agoAh, good point on the RPC stuff! That suggests pretty much mandatory use of keep-alive headers in infrastructure services, no?