News: 1744318129

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Return of Redis creator bears fruit with vector set data type

(2025/04/10)


The return of Redis creator Salvatore Sanfilippo has borne fruit in the form of a new data type - vector sets - for the widely used cache-turned-multi-model database.

Inspired by sorted sets, one of Redis' core data types known for handling ordered collections, vector sets offer a native way to store and query high-dimensional embeddings, with a focus on vector similarity search for AI workloads.

Redis started life in 2009 as an attempt to build a performant key-value database. By late 2020, it was [1]the most popular database on AWS , thanks to its popularity as a cache and message broker in cloud-native application stacks. Redis has since broadened its ambitions, [2]adding features for machine learning and support for JSON documents in a bid to evolve beyond its caching roots.

[3]

Sanfilippo, better known by the nickname antirez, [4]stepped down as the maintainer of Redis in mid-2020, [5]saying he wanted to focus on writing code rather than managing the project.

[6]

[7]

He returned in December last year to become “a bridge between the company and the community, but also somebody that could produce programming demos, invent and describe new patterns, write documentation, videos and blog posts about new and old stuff,” [8]according to his blog, referring to Redis the company that continues to steer development of the software.

The new data type is the result of Sanfilippo's return, and builds on Redis's sorted sets by enabling storage and querying of high-dimensional vector embeddings - commonly used in generative AI apps to represent semantic meaning in LLMs, for example.

[9]

Redis already supports vector similarity search through its Query Engine, introduced in 2023, which allows developers to find vectors most similar to a target input based on proximity metrics like cosine similarity.

Rowan Trollope, CEO of Redis, told The Register that vector sets expose a lower-level API, giving developers more direct control over the underlying vector data - a shift aimed at flexibility and performance.

“It’s extremely fast, easy to compose, and flexible in terms of how you implement it in your application. It's very much in keeping with the Redis ethos. Sanfilippo had to rewrite the entire underpinnings of the vector database which is called HNSW - hierarchical, navigable, small worlds - as a new algorithm,” he said.

[10]

Vector sets land in beta form as part of the Redis 8 Community Edition in May, with features and APIs subject to change based on feedback.

[11]Majority of Redis users considering alternatives after less permissive licensing move

[12]Linux Foundation marshals support for open source alternative to Redis

[13]Redis tightens its license terms, pleasing basically no one

[14]Redis justifies open source shift with fresh hardware, LLM cost-saving features

Redis has also [15]announced LangCache, which is described as a semantic caching service for AI apps and agents. The goal is to reduce expensive and latency-prone calls to LLMs by caching previous responses to semantically similar queries.

LangCache is set to launch as a fully managed REST service that sits between the application and the LLM, intercepting requests to serve cached responses when possible.

“It's not as straightforward as caching in the database world when you have a deterministic query, like a SQL string. In the case of a language model, you need a probabilistic or semantic cache, and so we use our vector database underneath the covers for that with a fine-tuned embedding model that's optimized for caching,” Trollope told us. ®

Get our [16]Tech Resources



[1] https://www.theregister.com/2020/11/23/redis_the_most_popular_db_on_aws/

[2] https://www.theregister.com/2021/04/21/redis_7/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/databases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Z_g_fzzVZggAx8dtVS4lBgAAANQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://www.theregister.com/2020/06/30/redis_creator_antirez_quits/

[5] https://antirez.com/news/133

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/databases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z_g_fzzVZggAx8dtVS4lBgAAANQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/databases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z_g_fzzVZggAx8dtVS4lBgAAANQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[8] https://antirez.com/news/144

[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/databases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z_g_fzzVZggAx8dtVS4lBgAAANQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/databases&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z_g_fzzVZggAx8dtVS4lBgAAANQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[11] https://www.theregister.com/2024/09/20/redis_users_considering_alternatives/

[12] https://www.theregister.com/2024/04/03/open_source_redis_alternative/

[13] https://www.theregister.com/2024/03/22/redis_changes_license/

[14] https://www.theregister.com/2024/09/12/redis_justifies_open_source_shift/

[15] https://redis.io/blog/spring-release-2025/

[16] https://whitepapers.theregister.com/



It is a very humbling experience to make a multimillion-dollar mistake, but
it is also very memorable. I vividly recall the night we decided how to
organize the actual writing of external specifications for OS/360. The
manager of architecture, the manager of control program implementation, and
I were threshing out the plan, schedule, and division of responsibilities.
The architecture manager had 10 good men. He asserted that they
could write the specifications and do it right. It would take ten months,
three more than the schedule allowed.
The control program manager had 150 men. He asserted that they
could prepare the specifications, with the architecture team coordinating;
it would be well-done and practical, and he could do it on schedule.
Furthermore, if the architecture team did it, his 150 men would sit twiddling
their thumbs for ten months.
To this the architecture manager responded that if I gave the control
program team the responsibility, the result would not in fact be on time,
but would also be three months late, and of much lower quality. I did, and
it was. He was right on both counts. Moreover, the lack of conceptual
integrity made the system far more costly to build and change, and I would
estimate that it added a year to debugging time.
-- Frederick Brooks Jr., "The Mythical Man Month"