Redis 8.0 Unveiled: New AGPLv3 License, Vector Search, JSON & More

On May 1, 2025 Redis 8.0 was officially released, bringing a leap in performance and major breakthroughs in open‑source licensing, data structures, and the query engine.

1 Open Source License Innovation: AGPLv3 Embraces Community

Redis 8.0 adds the OSI‑approved AGPLv3 license alongside the existing RSALv2/SSPLv1, marking a return to the open‑source community after previous licensing controversies.

License Background In March 2024 Redis 7.4 switched from BSD to a dual RSALv2/SSPLv1 model to limit free commercial use by cloud providers, which caused community split and forks such as Valkey.

AGPLv3 Significance AGPLv3 requires network users to share modifications, protecting Redis innovation while aligning with open‑source principles.

User Impact Developers can choose the license that fits their compliance needs, reducing enterprise risk and encouraging contributions.

2 Data Structure Explosion: 8 New Types Covering AI to Time Series

Redis 8.0 introduces eight native data structures, turning it into a versatile platform for AI, big data, and real‑time analytics.

2.1 Vector Set: AI‑Era Similarity Search Engine

Core Function Designed for high‑dimensional vector embeddings, supporting storage and queries for recommendation systems, semantic search, and image retrieval.

Technical Highlights Leverages Sorted Set design for range queries. Integrates Redis Query Engine for real‑time vector search. Benchmarks show 66k‑160k vector inserts per second depending on precision.

Application Example E‑commerce recommendation calculates user preference similarity to push precise product suggestions.

Below is a complete example of an e‑commerce recommendation system using Redis 8.0 vector sets.

Step 1: Create Vector Index

<code># Create an index named "product_index" with a 768‑dim FLOAT32 vector using cosine similarity
FT.CREATE product_index
  ON HASH
  PREFIX 1 "product:"
  SCHEMA
    id NUMERIC
    title TEXT
    category TEXT
    embedding VECTOR HNSW 6 TYPE FLOAT32 DIM 768 DISTANCE_METRIC COSINE
</code>

Step 2: Insert Product Data

<code># Insert product 1 (wireless Bluetooth headphones)
HSET product:1 id 1 title "无线蓝牙耳机" category "electronics" embedding "\x00\x01\x02..."
FT.ADD product_index product:1 VECTOR 0.1 0.2 0.3 ...
# Insert product 2 (smartwatch)
HSET product:2 id 2 title "运动手表" category "electronics" embedding "\x03\x04\x05..."
FT.ADD product_index product:2 VECTOR 0.4 0.5 0.6 ...
# Insert product 3 (coffee machine)
HSET product:3 id 3 title "咖啡机" category "home" embedding "\x06\x07\x08..."
FT.ADD product_index product:3 VECTOR 0.7 0.8 0.9 ...
</code>

Step 4: Execute Similarity Search

<code># Simulated user query vector (e.g., behavior vector for a smartwatch)
FT.NEARESTNEIGHBORS product_index VECTOR 0.4 0.5 0.6 0.7 ... K 2 FILTER @category:electronics
</code>

Output (simulated):

<code>1) (integer) 2  # product ID 2 (smartwatch) "score" -> 0.9876
2) (integer) 1  # product ID 1 (headphones) "score" -> 0.8765
</code>

2.2 Native JSON Support: Structured Data Operations Revolution

Core Function Store and manipulate JSON documents directly without serialization.

Technical Highlights Supports JSONPath for precise nested field access. Atomic update commands such as JSON.SET allow partial modifications. Combined with the query engine for secondary indexing of JSON fields.

Application Example IoT platforms store device metadata and quickly filter specific attributes via JSONPath.

<code># Store device metadata with nested structure
JSON.SET device:1001 $ '{"id":1001,"type":"sensor","location":{"room":"A1","floor":3},"metrics":{"temperature":25.6,"humidity":60}}'
# Query device temperature
JSON.GET device:1001 $.metrics.temperature
# Batch get room info for multiple devices
JSON.MGET device:1001 device:1002 $.location.room
# Atomically update humidity
JSON.SET device:1001 $.metrics.humidity 65
</code>

2.3 Time Series: IoT and Financial Data Powerhouse

Core Function Optimized storage for time‑series data with automatic compression and down‑sampling.

Technical Highlights Designed for high‑frequency data such as sensor readings or stock prices. Integrates probabilistic data structures for fast aggregation queries. Compatible with Prometheus and other monitoring systems.

Application Example Financial risk systems analyze transaction anomalies using time‑series analysis.

<code># Create a time‑series collection (retain 7 days, compressed encoding)
TS.CREATE stock:AAPL RETENTION 604800 ENCODING COMPRESSED
# Add stock price data
TS.ADD stock:AAPL 1728000000000 185.2  # timestamp (ms), price
TS.ADD stock:AAPL 1728003600000 186.1
# Query last hour data
TS.RANGE stock:AAPL -3600000 0
# Compute 1‑minute price volatility
TS.MRANGE 1728000000000 1728003600000 FILTER sensor_id=2 WITHLABELS AGGREGATION STDDEV 60000
</code>

2.4 Five Probabilistic Data Structures: Big Data Efficiency Tools

Bloom Filter Fast existence checks with a configurable false‑positive rate.

Cuckoo Filter Bloom‑like filter that supports deletions.

Count‑min Sketch Estimates element frequencies for Top‑K queries.

Top‑K Tracks the most frequent K elements in a data stream in real time.

t‑Digest Accurately computes quantiles such as median or P99.

3 Query Engine Refactor: 16× Performance Boost, Horizontal Scaling

Performance Leap Multi‑threaded query execution yields up to 16× throughput. Horizontal scaling in cluster mode enables linear read/write growth for massive datasets. Command latency reduced for 90 commands by 5.4%‑87.4% (max 87.4%).

Feature Extensions Secondary indexes for precise Hash and JSON field matching and range queries. Full‑text search with stemming, synonyms, and fuzzy matching. Integrated vector search for AI‑driven similarity retrieval.

4 Performance & Scalability: Throughput Doubled, Replication Latency Cut

I/O Multithreading Configuring io-threads can increase throughput by up to 112% on multi‑core CPUs. Example: 8‑thread setup roughly doubles operations per second.

Replication Optimizations Parallel replication streams reduce master‑slave sync time by 18%. Master write rate improves by 7.5%, peak buffer usage drops 35%.

Memory Efficiency Enhanced compression algorithms lower memory fragmentation. Hybrid storage (DRAM+SSD) via Redis Flex cuts costs.

5 Security & Ecosystem: Fine‑Grained Controls, AI Assistant

Security Enhancements ACL now includes @search and @json permission categories. Critical vulnerabilities such as CVE‑2025‑21605 patched.

Ecosystem Integration Redis Copilot – an AI‑driven development assistant that generates queries and code. Seamless data integration with MySQL, PostgreSQL, and CDC support. Cloud‑native offerings: Alpine/Debian Docker images and a Kubernetes Operator.

6 Upgrade Recommendations: Which Scenarios Must Upgrade?

AI/ML Workloads Vector sets and JSON dramatically speed up model inference.

Real‑Time Analytics Time series and probabilistic structures accelerate streaming data processing.

High‑Concurrency Systems I/O multithreading and replication improvements lower latency.

Security‑Sensitive Environments Fine‑grained ACLs and patched vulnerabilities boost compliance.

7 Future Outlook: Redis 8.0 and Beyond

Vector Search Support for distributed indexes and ANN algorithms.

SQL Compatibility Extended query syntax with JOIN support.

Cloud‑Native Features Enhanced serverless support and multi‑region replication.