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 "what if" where we'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's where Arrow would come in
It would be straightforward to wrap this as an Arrow Flight (Arrow over gRPC) endpoint. But it would make it heavier and less browser-compatible.
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'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.
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 "what if" where we'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's where Arrow would come in
It 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/2 connection to send arrow IPC. Which seems pretty pragmatic.
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't provide grpc endpoints yet?
You’re right, I got Arrow IPC confused with Arrow Flight