# valkey

Valkey is an open-source, high-performance in-memory key/value datastore and data-structure server used for databases, caching, message brokering, and streaming.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache

DevFeed: [Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache](<https://devfeed.tech/articles/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache-144311.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache/>)

Author: Paul Ross

Published: 2026-11-19T18:39:15Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-managed-grafana](<https://devfeed.tech/tags/amazon-managed-grafana.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [latency](<https://devfeed.tech/tags/latency.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node](<https://devfeed.tech/tags/node.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [query](<https://devfeed.tech/tags/query.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache for Valkey sends engine and host metrics to CloudWatch in OpenTelemetry format without an exporter or collector. The article demonstrates using ElastiCache Insights to locate a hot shard or node, then PromQL to rank nodes, inspect command latency, and alarm across all nodes as cluster membership changes. Standard monitoring publishes core metrics every 60 seconds; selected detailed metrics arrive every 15 seconds and can expose short latency spikes that a longer window smooths out. Core metrics and ElastiCache Insights are free, while selected detailed metrics, PromQL API scans, and alarms incur charges. The walkthrough requires a node-based Valkey cluster in a supported Region; its Grafana guidance covers version 13 or later, with a separate Prometheus data source approach for version 12.4.

### Source excerpt

Amazon ElastiCache for Valkey now offers OpenTelemetry metrics, detailed monitoring, ElastiCache Insights, and PromQL. This post walks through one troubleshooting path: turn on detailed monitoring, find a hot shard, query with PromQL, catch a short latency spike, and create one alarm that watches every node.

## Valkey 9.2 Delivers More Performance, Zstd Compression & Lower Memory Overhead

DevFeed: [Valkey 9.2 Delivers More Performance, Zstd Compression & Lower Memory Overhead](<https://devfeed.tech/articles/valkey-9-2-delivers-more-performance-zstd-compression-lower-memory-overhead-143043.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/Valkey-9.2>)

Author: Michael Larabel

Published: 2026-11-19T10:41:47Z

Content type: release

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Compression](<https://devfeed.tech/topics/compression.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [compression](<https://devfeed.tech/tags/compression.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [memory](<https://devfeed.tech/tags/memory.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [performance](<https://devfeed.tech/tags/performance.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [replication](<https://devfeed.tech/tags/replication.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [zstd](<https://devfeed.tech/tags/zstd.md>)

### AI overview

Valkey 9.2 combines performance work with changes aimed at reducing memory overhead. It adds B+ tree sorted sets, Zstd compression for RDB persistence and replication (described as achieving greater compression ratios than existing LZ4), forkless snapshotting and full synchronization to replicas, and server-side hot key detection. The new DELEX command conditionally deletes a string key when its value matches or differs from a given value. The excerpt also notes other optimizations and dozens of bug fixes.

### Source excerpt

Valkey 9.2 is out today as the latest feature update to this leading fork of the Redis in-memory, key-value database...

## Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache

DevFeed: [Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache](<https://devfeed.tech/articles/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache-142000.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache/>)

Author: Meet Bhagdev

Published: 2026-11-18T23:45:25Z

Content type: release

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Self Hosted AI Tools](<https://devfeed.tech/topics/self-hosted-ai-tools.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [TensorRT-LLM](<https://devfeed.tech/topics/tensorrt-llm.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [benefits](<https://devfeed.tech/tags/benefits.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [distributed-kv](<https://devfeed.tech/tags/distributed-kv.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [inference-costs](<https://devfeed.tech/tags/inference-costs.md>), [llm-inference](<https://devfeed.tech/tags/llm-inference.md>), [llm-inference-costs](<https://devfeed.tech/tags/llm-inference-costs.md>), [llms](<https://devfeed.tech/tags/llms.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-llms](<https://devfeed.tech/tags/self-hosted-llms.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Distributed KV caching with Amazon ElastiCache for Valkey adds a shared L2 tier across a GPU fleet, letting vLLM, SGLang, and TensorRT-LLM reuse prompt KV state when local GPU or host caches miss. An open-source LMCache connector requires a configuration change; cache.i8ge.48xlarge nodes use DRAM and NVMe tiering and RDMA over EFA. In tested workloads, gains depended on cache hits and prompt length: shared-document Q&A doubled requests per second and cut cost per million output tokens by 40% while meeting the stated interactivity targets; coding-agent and assistant throughput also increased. Reported TTFT reductions ranged from 55% to 93% across tested models. The post says the least benefit is expected for small deployments with KV state fitting in GPU memory, workloads without prompt reuse, and long outputs from short prompts. It recommends using the free KVTrace tool to estimate hit rate, savings, and cache size before deployment; estimates use hashed prompt data.

### Source excerpt

Today, we are announcing the general availability of distributed KV caching with Amazon ElastiCache for Valkey, a capability that cuts self-hosted LLM inference costs by up to 40% and time to first token by up to 80%. Learn how it works, review benchmark results across workloads and models, deploy it on your own GPU fleet, and size the savings with the open-source KVTrace tool.

## Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey

DevFeed: [Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey](<https://devfeed.tech/articles/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey-138649.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey/>)

Author: Varun Gautam

Published: 2026-11-17T23:39:18Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [valkey](<https://devfeed.tech/topics/valkey.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [hot-keys](<https://devfeed.tech/tags/hot-keys.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [minimal](<https://devfeed.tech/tags/minimal.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [serve](<https://devfeed.tech/tags/serve.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [write](<https://devfeed.tech/tags/write.md>), [write-through](<https://devfeed.tech/tags/write-through.md>)

### AI overview

DynamoDB caching for Amazon ElastiCache Serverless for Valkey routes supported DynamoDB SDK operations through a configured client, serving eventually consistent reads from cache and updating entries after writes reach DynamoDB. Strongly consistent reads bypass the cache and refresh it; unsupported operations and uncached tables go directly to DynamoDB. This can reduce hot-key read pressure and read charges, with sub-millisecond cache responses, while writes still incur DynamoDB costs. Setup requires a new Valkey 9+ serverless cache with DynamoDB caching enabled and IAM authentication, plus client configuration and permissions. The article's example estimates 40-46% lower monthly cost at 20,000 requests per second and a 90% hit rate, but says storage costs can outweigh savings below workload-dependent traffic thresholds; results depend heavily on hit rate and resident data size.

### Source excerpt

DynamoDB caching with Amazon ElastiCache Serverless for Valkey brings write-through caching to Amazon DynamoDB with sub-millisecond reads and minimal application changes. Serve hot keys from cache, reduce read throttling, and lower read costs while your application keeps calling the DynamoDB API as it does today.

## Redict deprecated in favor of Valkey

DevFeed: [Redict deprecated in favor of Valkey](<https://devfeed.tech/articles/redict-deprecated-in-favor-of-valkey-139340.md>)

Original publisher: [Read original article](<https://lwn.net/Articles/1108155/>)

Author: daroc

Published: 2026-11-17T16:20:44Z

Content type: news

Language: en

Sources: [LWN.net](<https://devfeed.tech/sources/lwn-net.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [community](<https://devfeed.tech/tags/community.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [file](<https://devfeed.tech/tags/file.md>), [fork](<https://devfeed.tech/tags/fork.md>), [license](<https://devfeed.tech/tags/license.md>), [linux-foundation](<https://devfeed.tech/tags/linux-foundation.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [package](<https://devfeed.tech/tags/package.md>), [redis](<https://devfeed.tech/tags/redis.md>), [switch](<https://devfeed.tech/tags/switch.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Drew DeVault has deprecated Redict, saying it could not build a sustainable community amid Valkey's success and Redis's return to a copyleft license. He recommends switching to Valkey, a permissively licensed Redis fork supported by the Linux Foundation; the projects are described as mutually compatible, with migration requiring a package change and configuration-file rename. He advises against returning to Redis, arguing that its contributor license agreement could enable another license change during financial difficulty.

### Source excerpt

Drew DeVault has announced that Redict, a fork of Redis that was created in response to Redis's 2024 license change, has been deprecated. He recommends switching to Valkey, the permissively licensed Redis fork supported by the Linux Foundation. The two projects are mutually compatible, so switching should be as simple as changing which package is installed and renaming the configuration file. I had hoped to rally the Redis diaspora around a copyleft initiative, to protect ourselves from future rug-pulls, and made Redict to serve this purpose. However, with the valkey project's success, and Redis's return to a copyleft license, Redict was not able to build a sustainable community. We recommend that Redict users switch to valkey, which uses a permissive license but has better long-term prospects. We advise against switching back to Redis; though it is once again open source, and copyleft, it uses a contributor license agreement which will facilitate another rug-pull when Redis has a bad financial quarter.

## How Flickr modernized caching with Amazon ElastiCache for Valkey

DevFeed: [How Flickr modernized caching with Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey-129585.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey/>)

Author: Wilson Lam

Published: 2026-11-11T15:54:48Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [end-user](<https://devfeed.tech/tags/end-user.md>), [failover](<https://devfeed.tech/tags/failover.md>), [layer](<https://devfeed.tech/tags/layer.md>), [more](<https://devfeed.tech/tags/more.md>), [moving](<https://devfeed.tech/tags/moving.md>), [over](<https://devfeed.tech/tags/over.md>), [post](<https://devfeed.tech/tags/post.md>), [redis](<https://devfeed.tech/tags/redis.md>), [team](<https://devfeed.tech/tags/team.md>), [this](<https://devfeed.tech/tags/this.md>), [user](<https://devfeed.tech/tags/user.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Flickr moved more than 40 Redis clusters behind Twemproxy to cluster-mode Amazon ElastiCache for Valkey deployments, replacing Predis with PhpRedis and enabling multi-AZ automatic failover. Valkey's Redis OSS API compatibility through version 7.2 allowed an in-place engine swap without application changes or data migration. For topology changes, Flickr rolled out workload by workload, starting with regenerable data; data-sensitive workloads were copied with RIOT, using scan mode for bulk replication and live mode to keep data synchronized. A rollout exposed temporarily stale cached content from keys that had not synchronized, prompting targeted database backfill and use of RIOT compare mode before later cutovers. On the most fragmented workload, increasing RIOT threads and reducing batch size resolved stalled replication. After consolidation, Flickr reports monthly ElastiCache spend fell about 5%, despite improved replication and failover; parallel clusters temporarily raised costs during the migration.

### Source excerpt

Flickr, part of SmugMug, serves over 100 million photographers. In this post, the Flickr team shares how they modernized their caching layer by migrating from Redis and Twemproxy to Amazon ElastiCache for Valkey, consolidating more than 40 clusters, enabling cluster mode and multi-AZ failover, and moving to PhpRedis, all with no end-user disruption.

## Dell PowerEdge R9825 Review: 512 Venice Cores in an Air-Cooled 3U Server

DevFeed: [Dell PowerEdge R9825 Review: 512 Venice Cores in an Air-Cooled 3U Server](<https://devfeed.tech/articles/dell-poweredge-r9825-review-512-venice-cores-in-an-air-cooled-3u-server-127585.md>)

Original publisher: [Read original article](<https://www.storagereview.com/review/dell-poweredge-r9825-review>)

Author: Brian Beeler

Published: 2026-11-10T22:13:29Z

Content type: article

Language: en

Sources: [StorageReview.com](<https://devfeed.tech/sources/storagereview-com.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [dell](<https://devfeed.tech/topics/dell.md>), [ddr5](<https://devfeed.tech/topics/ddr5.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [NUMA](<https://devfeed.tech/topics/numa.md>), [Parallelism](<https://devfeed.tech/topics/parallelism.md>), [Processor Affinity](<https://devfeed.tech/topics/processor-affinity.md>)

Tags: [7-zip](<https://devfeed.tech/tags/7-zip.md>), [aes](<https://devfeed.tech/tags/aes.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [amd](<https://devfeed.tech/tags/amd.md>), [amd-epyc](<https://devfeed.tech/tags/amd-epyc.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [arm](<https://devfeed.tech/tags/arm.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [ddr5](<https://devfeed.tech/tags/ddr5.md>), [dell](<https://devfeed.tech/tags/dell.md>), [dell-poweredge](<https://devfeed.tech/tags/dell-poweredge.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [epyc](<https://devfeed.tech/tags/epyc.md>), [memory](<https://devfeed.tech/tags/memory.md>), [processors](<https://devfeed.tech/tags/processors.md>), [review](<https://devfeed.tech/tags/review.md>), [server](<https://devfeed.tech/tags/server.md>), [socket](<https://devfeed.tech/tags/socket.md>), [threads](<https://devfeed.tech/tags/threads.md>), [venice](<https://devfeed.tech/tags/venice.md>)

### AI overview

The Dell PowerEdge R9825 fits two 600W EPYC 9996 processors (512 Zen 6c cores total) into an air-cooled 3U chassis, using stacked processor boards, shaped front intake and five hot-swap fans. It supports up to 8TB of 8,000MT/s RDIMMs or up to 4TB of 12,800MT/s MRDIMMs; testing on an AMD reference platform found about 1.9TB/s STREAM Triad bandwidth with MRDIMMs versus 1.2TB/s on the review unit, making memory choice consequential for bandwidth-bound work. The server offers PCIe Gen6 slots and up to 32 E3.S Gen6 bays, though 32-bay capacity was not available at launch. In measured workloads it substantially outperformed the prior 2U R7725 on GROMACS, OpenFOAM and multithreaded compression, while 3U yields fewer cores per rack unit. The excerpt also reports lower results in thread-count-sensitive JVM and scheduler tests, and weaker remote-socket bandwidth than NVIDIA Vera. Dell supports air cooling up to 35°C inlet across listed processors; higher temperatures restrict memory and GPU configurations, and at 45°C the listed processors require liquid cooling.

### Source excerpt

The Dell PowerEdge R9825 is the first server built on AMD's 6th Gen EPYC to reach our lab, and it is the dual-socket flagship of Dell's 18th generation PowerEdge line. Two EPYC 9996 processors give it 512 Zen 6c cores and 1,024 threads, 32 DDR5 slots take it to 8TB of memory, and the front The post Dell PowerEdge R9825 Review: 512 Venice Cores in an Air-Cooled 3U Server appeared first on StorageReview.com.

## Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey

DevFeed: [Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/topstep-s-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey-123996.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/topsteps-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey/>)

Author: Gbeminiyi Abolarin

Published: 2026-11-09T16:59:06Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [cname](<https://devfeed.tech/tags/cname.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [migration](<https://devfeed.tech/tags/migration.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [tls](<https://devfeed.tech/tags/tls.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Topstep moved about 53 million keys from a single-node Redis OSS 7.4 instance to a Multi-AZ Amazon ElastiCache for Valkey 7.2.6 cluster using RedisShake in PSYNC mode. Since its source version fell outside the managed migration's supported range and the team required a blue/green rollback path, it replicated commands across peered VPCs, validated key counts and application behavior, then cut over by changing a Route 53 record. The change took seconds; the source remained available during a soak period. Valkey's protocol compatibility avoided code changes apart from TLS configuration. Because the custom DNS name did not match the cluster certificate, Topstep kept CA verification enabled while validating against an allowlist of AWS endpoint names. The team reports automatic Multi-AZ failover, managed patching and backups, read P99 latency around 1.25 ms and write P99 around 0.5 ms, and 1-2 engineer-days per month freed from maintenance.

### Source excerpt

Topstep migrated roughly 53 million keys from self-managed Redis OSS to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster. Using RedisShake and a single Amazon Route 53 DNS change, the team completed a blue/green cutover in seconds with no application code changes beyond a small TLS configuration update.

## 6 Best Platforms for Semantic Caching in Enterprise LLM Apps

DevFeed: [6 Best Platforms for Semantic Caching in Enterprise LLM Apps](<https://devfeed.tech/articles/6-best-platforms-for-semantic-caching-in-enterprise-llm-apps-118610.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/platforms-for-semantic-caching-in-enterprise-llm-apps/>)

Author: Lyzr Team

Published: 2026-11-05T08:42:25Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [Large Language Model](<https://devfeed.tech/topics/llm.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apps](<https://devfeed.tech/tags/apps.md>), [best](<https://devfeed.tech/tags/best.md>), [caching](<https://devfeed.tech/tags/caching.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [llm](<https://devfeed.tech/tags/llm.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [semantic](<https://devfeed.tech/tags/semantic.md>)

### AI overview

Semantic caching can cut LLM costs, but similarity hits can confidently return another question's answer, so accuracy and request ordering matter more than hit rate alone. In the cited banking test, an ATM query received loan-balance instructions; AWS's benchmark still had roughly one incorrect cached answer in fourteen at a strict threshold. The excerpt compares four gateways--Lyzr OpenController, Kong AI Gateway, Azure API Management and Portkey--with Redis LangCache and ElastiCache for Valkey, which require teams to build surrounding policy and lookup logic. Their differences include where identity and guardrail checks run, tenant partitioning, exact-match behavior, threshold semantics, deployment and operational requirements. It recommends putting checks before lookups, scoping entries by tenant, avoiding response caching for changing claim status, and measuring false hits on real traffic. The article is available here as an excerpt, so this overview does not establish full-document coverage.

### Source excerpt

TL;DR In a test of 1,000 banking queries published on InfoQ in November 2025, a customer asking where to find an ATM was served instructions...

## What five P99 CONF talks reveal about database trade-offs

DevFeed: [What five P99 CONF talks reveal about database trade-offs](<https://devfeed.tech/articles/what-five-p99-conf-talks-reveal-about-database-trade-offs-107773.md>)

Original publisher: [Read original article](<https://thenewstack.io/p99-conf-database-tradeoffs/>)

Author: Doug Sillars

Published: 2026-10-30T13:00:00Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Database](<https://devfeed.tech/topics/database.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [scylladb](<https://devfeed.tech/topics/scylladb.md>), [valkey](<https://devfeed.tech/topics/valkey.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [applications](<https://devfeed.tech/tags/applications.md>), [azure](<https://devfeed.tech/tags/azure.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [high-performance](<https://devfeed.tech/tags/high-performance.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [p99-conf](<https://devfeed.tech/tags/p99-conf.md>), [performance](<https://devfeed.tech/tags/performance.md>), [post](<https://devfeed.tech/tags/post.md>), [scylladb](<https://devfeed.tech/tags/scylladb.md>), [sponsor-scylladb](<https://devfeed.tech/tags/sponsor-scylladb.md>), [sponsored](<https://devfeed.tech/tags/sponsored.md>), [sponsored-post](<https://devfeed.tech/tags/sponsored-post.md>), [storage](<https://devfeed.tech/tags/storage.md>), [talks](<https://devfeed.tech/tags/talks.md>), [trade](<https://devfeed.tech/tags/trade.md>), [virtual](<https://devfeed.tech/tags/virtual.md>)

### AI overview

The five talks show that database performance gains depend on workload and often shift costs elsewhere. Responsive's SlateDB uses immutable LSM files over object storage to reduce storage costs, while caching helps offset slower, priced object reads. ScyllaDB's optional Logstor targets read-intensive point lookups with one-I/O reads, trading more RAM and write work for speed; its reported benchmarks use different value sizes and are not direct comparisons. Valkey's lockless I/O queues raised throughput in Olson's tested workload, while atomic slot migration accelerated scaling; results are workload-specific. turbopuffer combines clustering and one-bit RaBitQ quantization to narrow vector searches, moving the bottleneck from storage bandwidth toward CPU, and relies on local SSD caches. TigerBeetle built a multi-cloud object-storage client to fit its single-core design; reported speedups apply to specified tests, and the custom client adds implementation work. Across the talks, each optimization introduces new costs, constraints, or bottlenecks.

### Source excerpt

P99 CONF is a virtual conference on high-performance, low-latency applications. Its 2026 event ran October 21-22. Here, we cover five The post What five P99 CONF talks reveal about database trade-offs appeared first on The New Stack.

## ZDI-26-833: Valkey clusterCreatePublishMsgBlock Numeric Truncation Error Remote Code Execution Vulnerability

DevFeed: [ZDI-26-833: Valkey clusterCreatePublishMsgBlock Numeric Truncation Error Remote Code Execution Vulnerability](<https://devfeed.tech/articles/zdi-26-833-valkey-clustercreatepublishmsgblock-numeric-truncation-error-remote-code-execution-vulnerability-106029.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-833/>)

Published: 2026-10-28T05:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [allows](<https://devfeed.tech/tags/allows.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [context](<https://devfeed.tech/tags/context.md>), [error](<https://devfeed.tech/tags/error.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [installations](<https://devfeed.tech/tags/installations.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-vulnerability](<https://devfeed.tech/tags/remote-code-execution-vulnerability.md>), [required](<https://devfeed.tech/tags/required.md>), [this](<https://devfeed.tech/tags/this.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Authenticated remote attackers can execute code as the Valkey service account by exploiting insufficient validation of parameters handled by the PUBLISH message handler. The flaw can cause an incorrect size calculation before buffer allocation. Valkey has issued an update to correct the vulnerability; the supplied excerpt does not identify affected versions or describe the update.

### Source excerpt

This vulnerability allows remote attackers to execute arbitrary code on affected installations of Valkey. Authentication is required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 8.8.

## P99 CONF 2026 Recap: A Tail of Two Days

DevFeed: [P99 CONF 2026 Recap: A Tail of Two Days](<https://devfeed.tech/articles/p99-conf-2026-recap-a-tail-of-two-days-102608.md>)

Original publisher: [Read original article](<https://www.scylladb.com/2026/10/27/p99-conf-2026-recap/>)

Author: Cynthia Dunlop

Published: 2026-10-27T15:53:35Z

Content type: article

Language: en

Sources: [ScyllaDB](<https://devfeed.tech/sources/scylladb.md>)

Topics: [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [QUIC](<https://devfeed.tech/topics/quic.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [High-Performance Computing](<https://devfeed.tech/topics/high-performance-computing.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [arrow](<https://devfeed.tech/tags/arrow.md>), [asia-pacific](<https://devfeed.tech/tags/asia-pacific.md>), [async](<https://devfeed.tech/tags/async.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [avi](<https://devfeed.tech/tags/avi.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azul](<https://devfeed.tech/tags/azul.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [p99-conf](<https://devfeed.tech/tags/p99-conf.md>), [recap](<https://devfeed.tech/tags/recap.md>)

### AI overview

P99 CONF 2026 kept its focus on tail latency while adding a dedicated Europe/India/Asia-Pacific track and featuring AI in roughly a dozen of its 60-plus talks. The recap highlights practical agent work, including Netflix's autonomous agent tracing inefficiencies in live services and proposing fixes, and a Redis experiment giving an agent a multicore cluster, profiles, MCP access and a budget to run performance tests. Other talks covered async I/O, databases, vector search, observability, networking and sandboxes. One reported performance comparison: TigerBeetle's Zig object-storage client, built with custom DNS, TLS, HTTP, single-threading, zero-copy and io_uring, was said to be 10 times faster than the AWS and GCP SDKs. The conference's pre-recorded talks with live audience chat are available on demand.

### Source excerpt

Our Aussie host's take on P99 CONF around the clock and (now) anytime on demand

## Nemo: Efficient Caching with Index Pushdown for Disaggregated OLTP Databases

DevFeed: [Nemo: Efficient Caching with Index Pushdown for Disaggregated OLTP Databases](<https://devfeed.tech/articles/nemo-efficient-caching-with-index-pushdown-for-disaggregated-oltp-databases-101504.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.33306>)

Author: Wenjie Hu, Xinjing Zhou, Zhihan Guo, Xiangpeng Hao, Xiangyao Yu

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>), [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [databases](<https://devfeed.tech/tags/databases.md>), [index](<https://devfeed.tech/tags/index.md>)

### AI overview

Nemo targets network bottlenecks in storage-disaggregated OLTP by pushing the full index to storage and caching hot records at compute. Its tree-structured record buffer combines caching and buffering for point and range queries, while caching negative search results reduces remote probes when a record is absent. Nemo also provides phantom protection without requiring knowledge of storage-side data layout. In the reported experiments, it outperformed page-based B+Tree and 2-Tree by up to 11.42x and 2.97x on positive point queries, and a hash-indexed record cache by up to 4.76x on negative searches. For phantom protection, it beat PCL by up to 1.55x in a dense key domain and maintained stable performance as the domain became large and sparse, where PCL degraded sharply.

### Source excerpt

arXiv:2610.33306v1 Announce Type: new Abstract: Storage-disaggregated databases decouple compute from storage, improving elasticity but suffering from network bottlenecks. Most cloud databases use page-based B+trees and buffer pools. Under disaggregation, each index traversal incurs serial network round-trips. Page-granularity transfers and caching also amplify network traffic and lower cache efficiency. Pushing down the full index to storage and caching only hot records at compute is appealing, but an efficient design must (1) provide a holistic record cache that accelerates both point and range queries, (2) mitigate the negative search penalty of confirming non-existence via remote probes, and (3) enforce phantom protection despite the index being encapsulated by the storage service. We introduce Nemo, a holistic index-and-buffer design optimized for storage-disaggregated OLTP with index pushdown. Nemo employs a tree-structured record buffer that unifies caching and buffering and accelerates both point and range queries. It further reduces the negative search penalty by caching negative search results. Nemo provides phantom protection that requires no knowledge of the storage-side data layout and is robust against large key domains, varying data skew, and partition schemes. Experiments show that Nemo outperforms page-based B+Tree and the state-of-the-art 2-Tree by up to 11.42x and 2.97x on positive point queries, and achieves up to 4.76x speedup on negative searches over a hash-indexed record cache. For phantom protection, Nemo outperforms PCL by up to 1.55x even under a dense key domain. Moreover, Nemo maintains stable performance while PCL degrades sharply as the key domain grows large and sparse.

## Yarrtube Keeps Your Favorite YouTube Channels on Your Server

DevFeed: [Yarrtube Keeps Your Favorite YouTube Channels on Your Server](<https://devfeed.tech/articles/yarrtube-keeps-your-favorite-youtube-channels-on-your-server-89765.md>)

Original publisher: [Read original article](<https://noted.lol/yarrtube/>)

Author: Jeremy

Published: 2026-10-18T19:38:19Z

Content type: article

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [Homelab](<https://devfeed.tech/topics/homelab.md>), [Jellyfin](<https://devfeed.tech/topics/jellyfin.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Fedora](<https://devfeed.tech/topics/fedora.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [docker](<https://devfeed.tech/tags/docker.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [jellyfin](<https://devfeed.tech/tags/jellyfin.md>), [self-hosted-media-streaming-audio-streaming](<https://devfeed.tech/tags/self-hosted-media-streaming-audio-streaming.md>), [yt-dlp](<https://devfeed.tech/tags/yt-dlp.md>)

### AI overview

Yarrtube follows selected YouTube channels and public playlists, downloads new videos with yt-dlp, and stores them on a server for a locally managed media collection. The article describes its browser interface, media-server integrations, Rust and SQLite implementation, Docker deployment, YouTube API key requirement, and lack of built-in authentication.

### Source excerpt

Keep selected YouTube channels and playlists on your own server with Yarrtube, a lightweight Docker app built around yt-dlp.

## Inside Hyperdrive: How we solved a rare Hyperdrive MySQL caching bug

DevFeed: [Inside Hyperdrive: How we solved a rare Hyperdrive MySQL caching bug](<https://devfeed.tech/articles/inside-hyperdrive-how-we-solved-a-rare-hyperdrive-mysql-caching-bug-86634.md>)

Original publisher: [Read original article](<https://blog.cloudflare.com/hyperdrive-mysql/>)

Author: Pranoy Dutta

Published: 2026-10-14T13:00:00Z

Content type: article

Language: en

Sources: [Cloudflare Blog](<https://devfeed.tech/sources/cloudflare-blog.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [cache-control](<https://devfeed.tech/topics/cache-control.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [hyperdrive](<https://devfeed.tech/tags/hyperdrive.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Cloudflare describes how it investigated and fixed a rare MySQL query caching bug in Hyperdrive while bringing MySQL support to general availability. The issue arose when Hyperdrive's Client and Endpoint nodes shared cached results encoded for different MySQL client capabilities. Storing canonical result bytes resolved the empty responses and raised Client connection success to 99.99%.

### Source excerpt

While adding MySQL support to Hyperdrive, we found a subtle protocol bug when caching query results. Here is how we tracked down a 0.001% rate error and made Hyperdrive MySQL generally available.

## Olson and Söderqvist Discuss Valkey's Evolution and Future Past Caching Use Cases at OSS EU

DevFeed: [Olson and Söderqvist Discuss Valkey's Evolution and Future Past Caching Use Cases at OSS EU](<https://devfeed.tech/articles/olson-and-soderqvist-discuss-valkey-s-evolution-and-future-past-caching-use-cases-at-oss-eu-83970.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/valkey-evolution/>)

Author: Olimpiu Pop

Published: 2026-10-09T09:09:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-cache](<https://devfeed.tech/tags/distributed-cache.md>), [durability](<https://devfeed.tech/tags/durability.md>), [news](<https://devfeed.tech/tags/news.md>), [redis](<https://devfeed.tech/tags/redis.md>), [replication](<https://devfeed.tech/tags/replication.md>), [security](<https://devfeed.tech/tags/security.md>), [storage](<https://devfeed.tech/tags/storage.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [valkey-evolution](<https://devfeed.tech/tags/valkey-evolution.md>)

### AI overview

The article reports on Valkey's development since its fork from Redis, covering throughput and memory-efficiency improvements, cluster features, and the GLIDE client library. It also discusses possible future directions, including synchronous replication and tiered storage, alongside release automation and security work.

### Source excerpt

Valkey is a growing project, launched as a fork of Redis over two years ago, supported by twelve maintainers and nine committee members from various companies. Recent developments include enhanced throughput, improved cluster functionality, and plans for features like synchronous replication and tiered storage. The project also emphasises security and release efficiency through automation. By Olimpiu Pop

## Percona develops Valkey-proxy to connect existing applications to Valkey clusters

DevFeed: [Percona develops Valkey-proxy to connect existing applications to Valkey clusters](<https://devfeed.tech/articles/redis-by-proxy-percona-targets-the-last-major-hurdle-to-valkey-adoption-77067.md>)

Original publisher: [Read original article](<https://thenewstack.io/valkey-proxy-redis-percona/>)

Author: Paul Sawers

Published: 2026-10-08T06:54:15Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Percona](<https://devfeed.tech/topics/percona.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [databases](<https://devfeed.tech/tags/databases.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [operations](<https://devfeed.tech/tags/operations.md>), [proxy](<https://devfeed.tech/tags/proxy.md>)

### AI overview

Percona is developing Valkey-proxy, an open source proxy designed to let existing applications connect to a Valkey Cluster without rewrites. The project targets organizations managing their own infrastructure and is moving into the Valkey project. General availability is planned for early 2027, with testing intended to uncover application compatibility issues.

### Source excerpt

When Redis changed its licensing in 2024, replacing its permissive BSD license with proprietary, source-available alternatives, it prompted a major The post Redis by proxy: Percona targets the last major hurdle to Valkey adoption appeared first on The New Stack.

## Valkey Memory Optimization, Version by Version and Encoding: How Many Bytes Did Each Release Actually Save?

DevFeed: [Valkey Memory Optimization, Version by Version and Encoding: How Many Bytes Did Each Release Actually Save?](<https://devfeed.tech/articles/valkey-memory-optimization-version-by-version-and-encoding-how-many-bytes-did-each-release-actually-save-61918.md>)

Original publisher: [Read original article](<https://www.percona.com/blog/valkey-memory-optimization/>)

Author: Percona Team

Published: 2026-09-29T15:33:33Z

Content type: article

Language: en

Sources: [Percona](<https://devfeed.tech/sources/blog-percona.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Encoding](<https://devfeed.tech/topics/encoding.md>), [Compression](<https://devfeed.tech/topics/compression.md>), [version](<https://devfeed.tech/topics/version.md>), [CPU Cache](<https://devfeed.tech/topics/cpu-cache.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cpu-cache](<https://devfeed.tech/tags/cpu-cache.md>), [memory-optimization](<https://devfeed.tech/tags/memory-optimization.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

A benchmark and source-code analysis compares memory use across Valkey versions 7.2.14 through 9.1.1. In the tested string-heavy workload, average key size fell from 102.48 bytes in 7.2.14 to 64.02 bytes in 9.1.1, a 37.5% reduction. The article attributes major changes to inline key storage and a redesigned hash table, while noting the results do not apply to every Valkey environment.

### Source excerpt

Introduction This RAM/Memory reduction is most useful for Valkey 9.1 environments that are key string heavy. They are used extensively in caching, sessions/authentication, real-time apps, ecomm, Ad tech/martech, and gaming. These scenarios see a reduction of 37.5%, which has been attained in our testing environments versus version 7.2.. The biggest jump in the reduction came ... Continued The post Valkey Memory Optimization, Version by Version and Encoding: How Many Bytes Did Each Release Actually Save? appeared first on Percona.

## Implement a correctness-safe Bloom filter lookup with Amazon ElastiCache for Valkey and Amazon Aurora PostgreSQL

DevFeed: [Implement a correctness-safe Bloom filter lookup with Amazon ElastiCache for Valkey and Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/implement-a-correctness-safe-bloom-filter-lookup-with-amazon-elasticache-for-valkey-and-amazon-aurora-postgresql-42098.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/implement-a-correctness-safe-bloom-filter-lookup-with-amazon-elasticache-for-valkey-and-amazon-aurora-postgresql/>)

Author: Chintan Agrawal

Published: 2026-09-17T16:01:43Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [bloom-filter](<https://devfeed.tech/topics/bloom-filter.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bloom-filter](<https://devfeed.tech/tags/bloom-filter.md>), [cache](<https://devfeed.tech/tags/cache.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-compatible](<https://devfeed.tech/tags/postgresql-compatible.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

This post explains a three-tier membership lookup that combines a Bloom filter in Amazon ElastiCache for Valkey, an exact-match cache, and Amazon Aurora PostgreSQL as the relational source of truth. The design provides fast negative checks and preserves correctness when false positives would affect business outcomes.

### Source excerpt

This post shows how to compose a Bloom filter with an exact-match cache and a relational source of truth into a three-tier, correctness-safe membership lookup using Amazon ElastiCache for Valkey and Amazon Aurora PostgreSQL, serving sub-millisecond decisions at peak throughput without false-positive risk.

## cognee 1.0

DevFeed: [cognee 1.0](<https://devfeed.tech/articles/cognee-1-0-80263.md>)

Original publisher: [Read original article](<https://dlthub.com/blog/cognee-1-0>)

Author: Adrian Brudaru

Published: 2026-06-26T00:00:00Z

Content type: release

Language: en

Sources: [DLT Hub](<https://devfeed.tech/sources/dlt-hub.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [parquet](<https://devfeed.tech/topics/parquet.md>), [OpenShell](<https://devfeed.tech/topics/openshell.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [community](<https://devfeed.tech/tags/community.md>), [data](<https://devfeed.tech/tags/data.md>), [open](<https://devfeed.tech/tags/open.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [rust](<https://devfeed.tech/tags/rust.md>)

### AI overview

Cognee 1.0 is an open-source memory system for AI agents, with a self-improving memory loop, Rust core, TypeScript SDK, and support for running on a single Postgres. The release also introduces Cognee Cloud and multi-tenant graph permissions. The article says the system can connect to agents including Claude Code, Cursor, and Codex.

### Source excerpt

cognee 1.0 is live: open-source memory for AI agents, now self-improving, with a Rust core and single-Postgres deployment. Cognee is a dltHub partner that uses dlt under the hood for loading structured data.

## What's new in Swift: April 2026 Edition

DevFeed: [What's new in Swift: April 2026 Edition](<https://devfeed.tech/articles/what-s-new-in-swift-april-2026-edition-2937.md>)

Original publisher: [Read original article](<https://swift.org/blog/whats-new-in-swift-april-2026/>)

Author: Dave Lester

Published: 2026-05-01T10:30:00Z

Content type: release

Language: en

Sources: [Swift.org](<https://devfeed.tech/sources/swift-org.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [swift-package](<https://devfeed.tech/topics/swift-package.md>), [Swift Testing](<https://devfeed.tech/topics/swift-testing.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [caching](<https://devfeed.tech/tags/caching.md>), [client](<https://devfeed.tech/tags/client.md>), [client-library](<https://devfeed.tech/tags/client-library.md>), [compile](<https://devfeed.tech/tags/compile.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [high-performance](<https://devfeed.tech/tags/high-performance.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [message-broker](<https://devfeed.tech/tags/message-broker.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [redis](<https://devfeed.tech/tags/redis.md>), [release](<https://devfeed.tech/tags/release.md>), [server](<https://devfeed.tech/tags/server.md>), [structured](<https://devfeed.tech/tags/structured.md>), [swift](<https://devfeed.tech/tags/swift.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

valkey-swift 1.0 is a Swift 6 client for Valkey that also works with Redis. It uses structured concurrency to scope connections and subscriptions for automatic cleanup, provides compile-time-checked typed command responses, and enables strict concurrency checking. Its standard command coverage is generated from Valkey's specifications. The release positions it as a new alternative to RediStack, whose pre-concurrency design would make retrofitting structured concurrency awkward; a migration guide is available. The digest also highlights Embedded Swift talks, a concurrency Q&A, libraries for robotics, TAR archives and XML, and Swift Evolution updates: a `FilePath` standard-library proposal under review and recently accepted networking, `UniqueBox` and test-reflection proposals.

### Source excerpt

Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. The 1.0 release of valkey-swift was recently announced on the Valkey blog. We've invited one of the authors to be this month's guest contributor: Hi, I'm Adam Fowler, an open source developer working in the Swift on server ecosystem. I am excited to announce the 1.0 release of valkey-swift - a production-grade Swift client for Valkey. Valkey is a high-performance datastore commonly used as a caching layer or message broker in server applications. It is an open source fork of Redis. Valkey-swift is a client library targeted at Valkey servers but is equally capable of working with Redis. It is built from the ground up with Swift 6 and structured concurrency. Every Valkey command returns typed responses checked at compile time, and strict concurrency checking is enabled throughout so that data races are caught by the compiler, not in production. Connections and subscriptions are all scoped through structured concurrency, so resources clean up automatically. The client covers every standard Valkey command, auto-generated from Valkey's own command specifications to stay in sync as the server evolves. Previously, the de facto client library for Redis was RediStack, which was built on top of pre-concurrency concepts. Retrofitting structured concurrency would have been awkward and some of the new features in valkey-swift infeasible. Around the same time Redis changed its licensing structure and the open source fork Valkey was created. So it felt like a good time to make a clean break and build a new library. If you're building server-side Swift and need a fast key-value store, add valkey-swift via Swift Package Manager, and you're ready to go. If you are using RediStack to connect with a Redis server, we have a guide to help you migrate to valkey-swift. Complete documentation is available, and contributions are welcome on GitHub. Now on to other news a

## What's new in Swift: April 2026 Edition

DevFeed: [What's new in Swift: April 2026 Edition](<https://devfeed.tech/articles/what-s-new-in-swift-april-2026-edition-91318.md>)

Original publisher: [Read original article](<https://www.swift.org/blog/whats-new-in-swift-april-2026/>)

Author: Dave Lester

Published: 2026-05-01T10:30:00Z

Content type: news

Language: en

Sources: [Swift.org](<https://devfeed.tech/sources/swift-org.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Swift Testing](<https://devfeed.tech/topics/swift-testing.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [swift-package](<https://devfeed.tech/topics/swift-package.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [broker](<https://devfeed.tech/tags/broker.md>), [caching](<https://devfeed.tech/tags/caching.md>), [client](<https://devfeed.tech/tags/client.md>), [compile](<https://devfeed.tech/tags/compile.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [covers](<https://devfeed.tech/tags/covers.md>), [high-performance](<https://devfeed.tech/tags/high-performance.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [licensing](<https://devfeed.tech/tags/licensing.md>), [manager](<https://devfeed.tech/tags/manager.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [redis](<https://devfeed.tech/tags/redis.md>), [release](<https://devfeed.tech/tags/release.md>), [specifications](<https://devfeed.tech/tags/specifications.md>), [swift](<https://devfeed.tech/tags/swift.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

valkey-swift 1.0 is a Swift 6 client for Valkey that also works with Redis. It uses structured concurrency, compile-time-checked typed command responses, and strict concurrency checking; connections and subscriptions are scoped for automatic cleanup. Its standard command coverage is generated from Valkey specifications. The author says this clean-slate design avoids retrofitting concurrency into RediStack's pre-concurrency foundation. The digest also highlights two Embedded Swift talks, a Swift concurrency Q&A, and libraries for robotics, TAR archives, and XML. Swift proposals include a `FilePath` addition under active review and accepted work on networking, `UniqueBox`, and customizable Swift Testing failure reflection. The supplied text is a digest excerpt and does not establish coverage of the full edition.

### Source excerpt

Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. The 1.0 release of valkey-swift was recently announced on the Valkey blog. We've invited one of the authors to be this month's guest contributor: Hi, I'm Adam Fowler, an open source developer working in the Swift on server ecosystem. I am excited to announce the 1.0 release of valkey-swift - a production-grade Swift client for Valkey. Valkey is a high-performance datastore commonly used as a caching layer or message broker in server applications. It is an open source fork of Redis. Valkey-swift is a client library targeted at Valkey servers but is equally capable of working with Redis. It is built from the ground up with Swift 6 and structured concurrency. Every Valkey command returns typed responses checked at compile time, and strict concurrency checking is enabled throughout so that data races are caught by the compiler, not in production. Connections and subscriptions are all scoped through structured concurrency, so resources clean up automatically. The client covers every standard Valkey command, auto-generated from Valkey's own command specifications to stay in sync as the server evolves. Previously, the de facto client library for Redis was RediStack, which was built on top of pre-concurrency concepts. Retrofitting structured concurrency would have been awkward and some of the new features in valkey-swift infeasible. Around the same time Redis changed its licensing structure and the open source fork Valkey was created. So it felt like a good time to make a clean break and build a new library. If you're building server-side Swift and need a fast key-value store, add valkey-swift via Swift Package Manager, and you're ready to go. If you are using RediStack to connect with a Redis server, we have a guide to help you migrate to valkey-swift. Complete documentation is available, and contributions are welcome on GitHub. Now on to other news a

## A Year of Innovation: DigitalOcean Managed Databases in 2025

DevFeed: [A Year of Innovation: DigitalOcean Managed Databases in 2025](<https://devfeed.tech/articles/a-year-of-innovation-digitalocean-managed-databases-in-2025-19906.md>)

Original publisher: [Read original article](<https://www.digitalocean.com/blog/managed-databases-updates-h2>)

Author: Nicole Ghalwash

Published: 2025-12-17T16:37:44Z

Content type: release

Language: en

Sources: [DigitalOcean](<https://devfeed.tech/sources/digitalocean.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Digital Ocean](<https://devfeed.tech/topics/digital-ocean.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [automation](<https://devfeed.tech/tags/automation.md>), [caching](<https://devfeed.tech/tags/caching.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cloud-management](<https://devfeed.tech/tags/cloud-management.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [commands](<https://devfeed.tech/tags/commands.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [databases](<https://devfeed.tech/tags/databases.md>), [digitalocean](<https://devfeed.tech/tags/digitalocean.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [managed](<https://devfeed.tech/tags/managed.md>)

### AI overview

The excerpt lists DigitalOcean Managed Databases releases in 2025, including PostgreSQL 17, MongoDB 8, larger MySQL and PostgreSQL storage limits, Valkey caching, MongoDB role-based access control, monitoring and hardening improvements, and Kafka Schema Registry support. It describes the August MCP Server in more detail: running locally, it lets AI tools such as Cursor or Claude manage cloud resources through natural-language commands, including provisioning Managed Databases. The publisher says this can reduce manual API calls and console navigation; the excerpt gives no further details about the other releases.

### Source excerpt

2025 was a big year for DigitalOcean Managed Databases, packed with meaningful enhancements designed to deliver more power, flexibility, and simplicity for developers and businesses of all sizes. With performance boosts and new database engines introduced to improve scalability, automation, and observability, this year's releases focused on making it easier than ever to build and run reliable data-backed applications on DigitalOcean. In this recap, we'll walk through the most impactful launches in both the first and second half of the year and how they help teams move faster while keeping complexity low. First, let's take a look at our releases in the first half of the year (H1): - Managed PostgreSQL support for v17 [February] - Managed MongoDB support for v8 [March] - Support for up to 20TB for Managed MySQL and 30TB for PostgreSQL [March] - Introducing DigitalOcean Managed Caching for Valkey [April] - Introducing Role-Based Access Control to DigitalOcean Managed MongoDB with Predefined Roles [May] - Database Observability, Monitoring, and Hardening Advancements [June] - Support for Kafka Schema Registry [July] The second half (H2) of 2025 saw even more big developments for DigitalOcean Managed Databases: MCP Server (August) The DigitalOcean MCP (Model Context Protocol) Server lets you manage your cloud resources using simple, natural-language commands through AI-powered tools like Cursor, Claude, or your own custom LLMs. Running locally, it streamlines tasks such as provisioning Managed Databases, making cloud operations faster, easier, and more intuitive for developers. DigitalOcean MCP Server marks a major step forward in bringing AI directly into cloud infrastructure workflows. It allows users to seamlessly integrate cloud management into AI assistants or custom-built agents while eliminating context switching, manual API calls, and constant console navigation. MCP Servers make managing cloud infrastructure with LLMs faster, more secure, and far more accessible

## Our Response to the RediShell Vulnerability

DevFeed: [Our Response to the RediShell Vulnerability](<https://devfeed.tech/articles/our-response-to-the-redishell-vulnerability-81931.md>)

Original publisher: [Read original article](<https://render.com/blog/response-to-redishell-cve-2025-49844>)

Published: 2025-10-08T19:59:00Z

Content type: news

Language: en

Sources: [Render](<https://devfeed.tech/sources/render.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [etcd](<https://devfeed.tech/topics/etcd.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [CVE-2021-44228](<https://devfeed.tech/topics/cve-2021-44228.md>)

Tags: [cve](<https://devfeed.tech/tags/cve.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [patch](<https://devfeed.tech/tags/patch.md>), [redis](<https://devfeed.tech/tags/redis.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Render says Redis and Valkey versions used by its Key Value instances are affected by the RediShell remote code execution vulnerability. It reports no evidence of exploitation on Render and has scheduled maintenance to upgrade instances to patched releases. Customers can run maintenance sooner; otherwise, it occurs at the scheduled time, with about one minute of unavailability expected.

### Source excerpt

We're scheduling maintenance for Render Key Value instances to patch this vulnerability and keep your infrastructure secure.

[Next page](<https://devfeed.tech/topics/valkey.md?cursor=WyIyMDI1LTEwLTA4VDE5OjU5OjAwKzAwOjAwIiwgImQwNGNjMmMyLTAxODEtNDE1Yy1iMTQwLTA5NDg0ZTU1MWYyZiJd>)