Migration playbook

The Radix and Sirin plugins give Picodata wire-protocol compatibility with Redis and Cassandra. Applications keep their code; only the database underneath changes.

From Redis → Radix

Radix implements the Redis wire protocol (RESP2) and the Redis Cluster client model. Most teams stop their Redis cluster, bring up Picodata with the Radix plugin enabled, and re-point client connection strings — no dual-write phase, since Redis is typically a cache.

  • Compatibility surface: 180+ Redis commands, RESP2, MOVED redirects.
  • Operational profile: run Radix as a volatile cache or as a persistent key-value store with WAL durability.
  • Limitations: Redis modules (RedisJSON, RediSearch, RedisGears) are not implemented yet.

Step-by-step instructions: Picodata documentation — Radix.

From Cassandra → Sirin

Sirin implements the Cassandra CQL wire protocol on top of Picodata's shard-per-core engine. Drivers and CQL queries continue to work; the data layer underneath becomes a Picodata cluster with Raft-replicated WAL.

  • Compatibility surface: CQL, native CQL drivers (Java, Python, Go, Node.js), client-side load balancing.
  • Data movement options: SSTable file import for offline migration, or streaming via Debezium + Kafka and the Franz plugin (Kafka reader) for online migration.
  • Consistency: Sirin defaults to strong consistency; Cassandra-style eventual consistency is also configurable.

Step-by-step instructions: Picodata documentation — Sirin.

Typical pilot timeline

  • Wire-compatibility migration (Redis or Cassandra) — 4–8 weeks end to end, including evaluation, schema mapping, performance verification, and cutover. Verified on production projects.
  • Platform migration (high-throughput application, in-memory analytics, multi-tenant workload) — 6 to 12 months, depending on architectural complexity and data volume.

Who runs the work

Most evaluators run pilots themselves. The Community Edition, the docs, and the open plugin SDK are enough for self-service evaluation.

For full turnkey deployments — sizing, capacity planning, schema migration, performance tuning, post-integration operations — the Picodata team partners with integrators on a per-engagement basis. Open an issue or write to hello@picodata.io to start the conversation.

Download Picodata → Read the docs