whirlwind-match/whirlwind-db — Issue #72: Radically reduce data transfer for search results to scores + ref in binary
Author: nealeoc
Created: 2011-10-14 20:42:53+00:00
State: open

Significant load on client and server will be around serialization of data to/from server.

We need a front end layer that can take a POJO and map the relevant bits into a whirlwind index, and the rest can go somewhere else for storage.

Our own annotations of what fields to index and map at client side would certainly be beneficial. Also, we can get screaming write perf if we remove the possibility of getting a KeyCollisionException by putting unique keys elsewhere. We just go on unique Ref (i.e. our own @Id)