1. The current performance bottleneck is round‑trip latency, not JSON deserialization
- “While Jev is fast, using it is hardly bottlenecked by deserializing from JSON.” – orf
- “With the API as it is today, the bottleneck is the thousands of round trips (one per state).” – ianmcook
2. Debate over the best serialization/transport approach (Arrow IPC, Arrow Flight, gRPC)
- “grpc is an RPC framework and Arrow IPC is a serialization format. You can use Arrow Flight which uses grpc to send Arrow IPC.” – mihevc
- “Using arrow is cool, but grpc seems like a more natural fit than arrow IPC and would give you the same benefits.” – orf
- “It would be straightforward to wrap this as an Arrow Flight (Arrow over gRPC) endpoint.” – ianmcook
3. Practical considerations and trade‑offs (HTTP/2 usage, weight, browser compatibility)
- “If I read the example correctly they are using long living http/2 connection to send arrow IPC. Which seems pretty pragmatic.” – mihevc
- “But it would make it heavier and less browser‑compatible.” – ianmcook