Agreed. With the API as it is today, the bottleneck is the thousands of round trips (one per state). The post is a bit of a &quot;what if&quot; where we&#x27;re imagining (and hoping!) that TypeSafe adds a batch endpoint, which would take the round trips out of the picture. Then serialization would start to matter, and that&#x27;s where Arrow would come inIt would be straightforward to wrap this as an Arrow Flight (Arrow over gRPC) endpoint. But it would make it heavier and less browser-compatible.

If I read the example correctly they are using long living http&#x2F;2 connection to send arrow IPC. Which seems pretty pragmatic.

You’re right, I got Arrow IPC confused with Arrow Flight

grpc is an RPC framework and Arrow IPC is a serialization format. You can use Arrow Flight which uses grpc to send Arrow IPC. But I suppose TypeSafe doesn&#x27;t provide grpc endpoints yet?

While Jev is fast, using it is hardly bottleknecked by deserializing from JSON.Using arrow is cool, but grpc seems like a more natural fit than arrow IPC and would give you the same benefits.

What if Jev spoke Arrow?