[Feature]: wasm bindings

[kesavkolla]

Problem / Motivation

It would be nice to bring the zvec to browser. Basically the index can be served from server and on browser we can perform search.

A decoupled solution basically building index is done in server side and on browser the index is loaded in memory and perform searches

Proposed Solution

Alternatives Considered

No response

Affected Area

No response

[zhourrr]

Thank you for your interest in zvec and for sharing this use case.

Could you elaborate a bit on your specific application or performance expectations for the client-side search?
For your current needs, would it make sense to start a vector database server on your remote server and communicate with it over the network to retrieve results? This way, both index building and searching happen on the remote server, and your local browser simply receives the search results.

We're planning to release Node.js integration soon. WASM is something we value and plan to explore. Any additional details you can provide would be very helpful, thanks!

[kesavkolla]

My specific use case is searching through documents and textual notes. My data is static which basically means I can compute index as a batch mode and store the index. I plan to compute this index per user as I need to search within one user documents only. That is the reason I want an ability to ship the index to the browser as soon as user logs into system. Then I can provide ability to search on client itself. This will reduce the network calls and also managing server side read/load of index for thousands of users. If I've to scale server side for several users then I will exhaust resources on server for keeping index in server memory. Client side is better because index lives on client memory.