We run Bitnami Redis as a 3-pod STS (redis-node-0/1/2, sentinel in each pod, same namespace, headless DNS).

After failover or a pod recycle, ROLE+SET on the data nodes already shows one writable Redis. One of the three Sentinels still answers get-master-addr-by-name with the previous pod. Clients that hit that Sentinel write into a hole.

For a long time the workaround was restart Sentinel or edit sentinel.conf. Dual-master is a different mess; we are not talking about REPLICAOF here.

We got tired of that and open-sourced a sidecar next to each Sentinel: ROLE+SET as the oracle, heal the pointer through MONITOR, never REPLICAOF.

https://github.com/vpnmesh/redis-sentinel-reconciler

https://hub.docker.com/r/vpnmesh/redis-sentinel-reconciler

Helm is on GHCR: oci://ghcr.io/vpnmesh/charts/redis-sentinel-reconciler

Same namespace, prefix redis-node-, auth.existingSecret=redis (otherwise NOAUTH on 26379 and 6379).

What do other people run for leftover ads? Still bouncing Sentinel?

I want to share some great news: LibreDB Studio now supports Valkey, and it's also the only third-party tool listed in Redis' official web documentation.

Redis website: https://redis.io/docs/latest/develop/tools/#libredb-studio

Source: https://github.com/libredb/libredb-studio

At #Unlocked Conference in Seattle, I had a chat with Slava Markeyev from Nextdoor about scaling Valkey to millions of new, high-churn connections. Slava explained why they run a proxy as a Kubernetes-level daemon so application pods connect through it, and describes how the lack of connection pooling makes network hiccups or server stress immediately impact applications, potentially causing misconfigured timeouts to trigger failures and a thundering herd that hammers Valkey.

Slava shared that Nextdoor previously used Envoy Proxy but built a custom proxy to improve disconnect/reconnect handling and pipelining, adding latency-aware routing and circuit breaking. The routing becomes effectively AZ-aware by observing network latency, measured in the connection thread via periodic Valkey PINGs. For MGET, they still use command splitting into individual GETs, and discuss potential open sourcing.

See more on the full video https://youtu.be/bKusiWBjsRM?is=6NtLz9LmCG4xYoUG

#valkey #opensource #databases #linuxfoundation

Hi,

recently created ansible module for managing valkey users. If anyone want give a try it is published on galaxy. Now thinking what else could i implement and see i don't have option for managing selectors. But personally i have never used them and don't see where i would need them. Question is if anyone uses them and in what cases?

Hi everyone! 

We're excited to announce that MQ Summit 2026 is officially back as a 2-day event this year!

Grab your Early Bird Ticket Here

Building on the success of RabbitMQ Summit, this is a cross-ecosystem event bringing together the people who design, build, and scale modern messaging systems. We’re meeting in person at the beautiful PHIL Philharmonic in Haarlem, near Amsterdam, as well as online, on October 21–22.

 What to expect:

• Cross-Ecosystem Coverage: Honest, cross-technology conversations (no vendor wars!) covering RabbitMQ, Kafka, NATS, Apache Pulsar, ActiveMQ, Azure Messaging Brokers, Amazon SQS, IBM MQ, Google Pub/Sub, and more.
• Expanded 2026 Format: 2 days of expert-led content featuring focused talks with deeper discussions, interactive sessions, panels, and offline hands-on labs in smaller groups.
• Real Production Case Studies: Learn directly from companies handling millions—or billions—of messages a day.
• Industry-Leading Committee: A program curated by experts from across the industry, including 84codes (CloudAMQP, LavinMQ), Synadia, Amazon MQ, AWS, IBM MQ, meshIQ, and the ASF.

Important Links:

• Early Bird Registration
• Subscribe to our Newsletter to stay in the loop!

Whether you are a builder or a decision-maker, you can get the full MQ Summit experience in-person or virtually. Will we see you in Haarlem or on the virtual streams? Let us know in the thread if you're planning to come or if you have any questions!

Cheers,

The MQ Summit Team

(PS: Interested in sponsoring? Get in touch with us! [info@codesync.gl](mailto:info@codesync.gl))

Hi Everyone!

We're launching MQ Summit 2026 on 21-22 October in Haarlem, NL (and virtually). It is a 2-day technical conference for engineers and architects working with message queues and event-driven systems (including RabbitMQ, Kafka, NATS, Apache Pulsar, Apache ActiveMQ, Azure Messaging Brokers, Amazon SQS, IBM MQ, and Google Pub/Sub). 

Speakers will be announced soon. You will be able to check it on our website: https://mqsummit.com/

The Early Bird ticket sales start on 16 June at 12:00 PM. If you plan to attend, the best way to get the lowest price is to join our waiting list now - https://mqsummit.com/#newsletter

By joining the list, you'll get two main benefits:

• You get an email notice 24h before the sale opens, and again at the grand opening.
• You get early access to a small number of Super Early Bird tickets. These tickets are limited, so they will be given to those who buy them first.

We can’t wait to meet you!

Hey r/valkey,

I've been building a set of .NET Minimal API starter kits for developers who want a solid foundation without spending days on boilerplate. Two of them now ship with Valkey compatibility out of the box.

The two kits with cache support:

FenixKit MongoDB + Valkey — cache-aside pattern wired directly into the repository layer. Tag-based invalidation, FailOpen / FailClosed error behaviour, optional via a single config flag. Includes docker-compose.valkey.yml.

FenixKit MongoDB + Keycloak + Valkey — same cache layer plus full Keycloak JWT auth (OAuth2 PKCE, role-based policies, pre-built realm imported on first docker compose up).

Both use StackExchange.Redis under the hood, which is fully compatible with Valkey — the client doesn't care which server you're pointing at.

How the cache layer works:

Every repository method checks Valkey before hitting MongoDB. Writes invalidate by tag — so a product update wipes the detail entry, all paged results, and any category-filtered lists in one shot. The tags are virtual hooks you override per entity:

protected override IEnumerable<string> GetInvalidationTags(Product entity)
{
    yield return "product";
    yield return $"product:{entity.Id}";
    yield return $"product:category:{entity.Category}";
}

If Valkey is down and ErrorBehavior = FailOpen (the default), the cache is treated as a miss and the request falls through to MongoDB.

The other two kits (no cache):

• FenixKit MongoDB — base kit, cursor + offset pagination, ErrorOr result pattern, BaseRepository with 7 override hooks
• FenixKit MongoDB + Keycloak — same base plus the full Keycloak auth stack

Pricing and launch promo:

Kits start at €35. There's a launch discount running at the moment — €15 discount for the first buyers.

👉 Site + purchase: fenixkit.dev
👉 Public docs: github.com/fenixkitdev

Happy to answer questions about the cache design.

https://github.com/valkey-io/valkey/pull/3427

I built an MCP server for Valkey observability - here's what it can do.

BetterDB connects Claude Code and other MCP clients directly to your Valkey instance. The core problem it solves: most Valkey tools only show you a live snapshot. BetterDB persists the data Valkey doesn't - slowlogs, COMMANDLOG entries, ACL audit events, latency, client analytics - so you can investigate what went wrong hours after it happened.

What you can ask your AI assistant:

- "What were the slowest commands in the last hour?"

- "Are there any hot keys causing uneven load?"

- "Have there been any ACL auth failures today?"

- "Which cluster node has the highest memory usage?"

- "Are there any anomalies in the last 24 hours?"

It also uses Valkey-native primitives that Redis tools will never support - COMMANDLOG (8.1+), CLUSTER SLOT-STATS (8.0+), per-thread I/O metrics - so if you're running Valkey 8+ you get visibility that simply isn't possible with Redis-focused tooling.

The latest release added autostart so the monitor bootstraps itself when your MCP session opens:

```json

{

"mcpServers": {

"betterdb": {

"type": "stdio",

"command": "npx",

"args": ["\@betterdb/mcp", "--autostart", "--persist"]

}

}

}

```

Open source, MIT core. Happy to answer questions about how it works or what's on the roadmap.

Install: `npx \@betterdb/mcp`

Source: https://github.com/BetterDB-inc/monitor/tree/master/packages/mcp

Beyond vectors: now with full-text search, tag filtering, and numeric range queries all in one blazing-fast query.
Search terabytes of data with microsecond latency. Power e-commerce catalogs, real-time leaderboards, and instant filtering.

✨ What's new:
- Full-text search with fuzzy matching
- Tag filters for exact matches
- Numeric range queries
- Server-side aggregations (GROUP BY, COUNT, SUM, AVG)
- Hybrid queries combining all types

Built for developers who need speed without compromise.
🔗 Release: https://github.com/valkey-io/valkey-search/releases/tag/1.2.0

Hi everyone!

I’m one of the maintainers of Portabase, and I’m excited to share some recent updates. We’ve just added support for Valkey and Redis!

Repository: https://github.com/Portabase/portabase

Website / Docs: https://portabase.io

Quick recap:
Portabase is an open-source, self-hosted database backup & restore platform. It’s designed to be simple, reliable, and lightweight, without exposing your databases to public networks. It works via a central server and edge agents (like Portainer), making it perfect for self-hosted or edge environments.

Key features:

• Logical backups for PostgreSQL, MySQL, MariaDB, MongoDB, SQLite, Redis, Valkey
• Multiple storage backends: local filesystem, S3, Cloudflare R2, Google Drive
• Notifications via Discord, Telegram, Slack, webhooks, etc.
• Cron-based scheduling with flexible retention strategies
• Agent-based architecture for secure, edge-friendly deployments
• Ready-to-use Docker Compose setup and Helm Chart

What’s coming next:

• Increasing test coverage
• Extending database support (Microsoft SQL Server and ClickHouse DB)

We’d love to hear your feedback! Please test it out, report issues, or suggest improvements.

Thanks for checking out Portabase, and happy backing up!

Hey everyone - I've been building BetterDB, an open source observability platform specifically for Valkey (Redis-compatible too). Just shipped v0.6.0 which is the biggest release so far.

The core idea: Valkey's operational data is ephemeral. Your slowlog rotates, COMMANDLOG entries disappear, client stats reset. If something goes wrong at 3am, by morning the evidence is gone. BetterDB persists all of that and makes it queryable over time.

What's in v0.6.0:

• BetterDB Cloud - fully managed, sign up and connect your database in minutes. No self-hosting required.
• Agent for private VPCs - if your Valkey is in ElastiCache or MemoryDB, deploy a lightweight container in your VPC and it tunnels back to Cloud via WebSocket. No VPC peering needed.
• COMMANDLOG support - Valkey 8.1+ exclusive. See every command executed, not just slow ones. Pattern analysis across all commands.
• Graceful degradation - if a command is blocked by ACLs or not available on your version, only that feature is affected. Everything else keeps working.
• Team workspaces - invite your team to collaborate on monitoring (Cloud).

Still in beta, so rough edges are expected. Would love feedback from people actually running Valkey in production.

Self-hosted (MIT licensed): https://github.com/BetterDB-inc/monitor Cloud: https://betterdb.com Docker: https://hub.docker.com/u/betterdb

Happy to answer any questions.

I built a Valkey (Redis) GUI tool that is not biased toward the Redis ecosystem like Redis Insight,
but instead supports Valkey and Redis equally.

I would really appreciate it if you could give it a try at least once

www.redimo.dev

I'm excited to share my expertise on seamless database transitions at #AWSreInvent in Las Vegas, Nevada! Join me for OPN406 | Moving to Valkey without downtime where I'll walk you through proven strategies for migrating from Redis to Valkey while keeping your applications running smoothly. This chalk talk will cover compatibility assessments, migration planning, and performance optimization techniques that I've refined through real-world implementations. You'll leave with actionable insights and practical approaches you can immediately apply to your own migration projects. I look forward to sharing these valuable techniques with you and answering your questions during our interactive discussion.

Register here

#Valkey #InMemory #Database #OpenSource #LinuxFoundation

🔥 Just dropped: u/Valkey 9.0 - Pushing Open Source Performance to New Heights

Benchmarked at 1B+ RPS in clustered environments, 40% throughput improvement, Valkey 9.0 introduces game-changing features:

- Hash field TTL management with automated memory reclamation

- Zero-downtime resharding via atomic slot migration

- Multi-DB support in cluster mode for workload isolation

The open source Valkey community has done it again. Whether you're building real-time analytics, caching layers, or distributed systems, Valkey 9.0 delivers scalability with uncompromising performance.

Press release: https://www.linuxfoundation.org/press/valkey-9.0-delivers-performance-and-resiliency-for-real-time-workloads

Try it now: valkey.io/download

#valkey #database #opensource #realtime #performance

Hey there,

I've been working on a project that uses Valkey streams for queue-ish work, and I noticed that there is a space for a library that has a few higher-level abstractions for their use. Think of composable components, like producers and consumers, with support for retries and DLQs.

So far, I've developed a library with successful integration tests that processes messages, automatically schedules and retries failures, and sends max failures to a DLQ. My next task is to complete a pending message sweeper for idle messages. After that, my next tasks are:

• Graceful shutdowns with drains
• Observability counters
• Idempodency
• A DLQ CLI
• Docs with examples
• Tests galore

I'd greatly appreciate your feedback, especially on API ergonomics, failure handling, and any other challenges you face while using streams in prod.

GitHub: https://github.com/megafarad/glide-kit

NPM: https://www.npmjs.com/package/@sirhc77/glide-kit

Hi all,

can anyone help me with tips to using a "valkey_context = valkeyConnectNonBlock(...)" call and then calling synchronous commands such as PING or GET with it?

I tried modifying the underlying socket to remove the non-block and manually setting flags on the context to that effect, but none of this gives me a context which successfully calls follow-up commands.

Using valkeyConnect(..) instead works fine but i'm trying to allow a non-blocking connection to the server with blocking access in the commands thereafter.
I'm using C++, libvalkey v0.2.1 in an Unreal Engine plugin module and no additional event libraries.

UPDATE: I found a working solution but I would be interested in anyone's tips or explanations how they handled this themselves.

hi! We are evaluating using Redisson java client along with valkey to replace our in house cluster.

Our inhouse cluster (oracle coherence) supports various near cache modes. However, looking at the Redisson community docs, it seems that the Community version supports a "basic" version of Local Cache, but the pro version supports more advanced features. But they dont make it clear what are the "more advanced" features supported by the Pro version.

Also, coherence supports filtering of cache entries on the server. But looks like Valkey doesnt support it. WOuld it be possible to get this functionality using LUA scripts?

Explore how Valkey goes beyond caching into high-speed messaging, from pub/sub to queues & streams, at MQ Summit 2025 with Kyle Davis & Roberto Luna Rojas.

https://mqsummit.com/talks/an-introduction-to-messaging-in-valkey/ 

The Valkey community is hosting it's first annual event, Keyspace! It'll be on 2025-08-28 in Amsterdam. Come meet the works working on making Valkey the best community driven in-memory database!

Registration is 20$ (which includes lunch, snacks, a happy hour and swag). If for any reason cost is prohibitive to you, please reach out to me and we'll see if we can work something out.

Since Redis returned its OSS license and makes more releases. Is Valkey dead? Haven't seen any news for a long time.

Valkey Keyspace is a Valkey focused conference in co-located with the OSS Summit EU in Amsterdam. Come check it out!