Comment by killthebuddha

I'm currently evaluating different vector stores and passed on Redis today after spending about a half day looking into it. Here's my reasoning

    1. The Node.js client is designed to be just a thin wrapper around Redis commands. The client's docs basically just point you straight at the Redis docs.

    2. The `@redis/search` API is slightly different than the FS.SEARCH Redis command's api. The difference is not documented and cost me ~20 minutes. This is a pretty big problem given item 1.

    3. The `@redis/search` TypeScript types didn't allow some valid FS.SEARCH calls.

One thing to note is that for some use cases (IMO probably a large fraction of use cases right now), the vectors are derived data, so you don't necessarily need a super robust/battle-tested "database", you just need something with a simple happy-path API.