valkey-glide
Valkey GLIDE - Skill Router
Parent router for the official Valkey GLIDE multi-language client skills. Each per-language skill is fully self-contained - it includes its own connection setup, data types, batching, PubSub, streams, OTel, TLS, error handling, performance tuning, and production best practices. No shared reference files exist at this level.
Routing
- Python setup, async/sync API, redis-py migration -> valkey-glide-python
- Java setup, CompletableFuture API, Spring -> valkey-glide-java
- Node.js setup, Promise/TypeScript API -> valkey-glide-nodejs
- Go setup, CGO, Result[T] API -> valkey-glide-go
- PHP setup, C extension, PIE/Composer -> valkey-glide-php
- C# setup, async/await, .NET 8.0+ -> valkey-glide-csharp
- Ruby setup, valkey-rb gem -> valkey-glide-ruby
- Switching from redis-py -> migrate-redis-py
- Switching from ioredis -> migrate-ioredis
- Switching from Jedis -> migrate-jedis
- Switching from Lettuce -> migrate-lettuce
- Switching from go-redis -> migrate-go-redis
- Switching from StackExchange.Redis -> migrate-stackexchange
More from avifenesh/valkey-skills
valkey
Use when building apps with Valkey - caching, sessions, queues, locks, rate-limiting, leaderboards, counters, pub-sub, streams, scripting. Covers IFEQ/DELIFEQ, hash field TTL, COMMANDLOG. Not for server internals (valkey-dev) or ops (valkey-ops).
5valkey-dev
Use when contributing to the Valkey server - C internals, event loop, commands, data structures, cluster, replication, RDB/AOF, memory, threading, modules, Lua, RESP, tests. Not for app development (valkey) or ops (valkey-ops).
5valkey-ops
Use when deploying, configuring, monitoring, or troubleshooting self-hosted Valkey. Covers Sentinel, cluster, persistence, replication, security, Kubernetes, performance tuning. Not for app development (valkey) or server internals (valkey-dev).
5valkey-ecosystem
Use when evaluating the Valkey ecosystem - client libraries, modules (JSON, Bloom, Search), managed services (AWS, GCP, Aiven), monitoring tools, frameworks (Spring, Django, Rails), Docker/Kubernetes deployment, CI/CD patterns, migration from Redis, and developer tooling.
5glide-mq
Use when building message queues with glide-mq. Covers queue setup, producer/consumer patterns, job scheduling, workflows, batch processing, streaming, and suspend/resume. Not for migrating from BullMQ (migrate-bullmq) or Bee-Queue (migrate-bee).
4migrate-go-redis
Use when migrating Go from go-redis to Valkey GLIDE. Covers Result[T] nil handling, CGO dependency, PubSub, SetWithOptions, Alpine/MUSL gotchas. Not for greenfield Go apps - use valkey-glide-go instead.
1