What's next: From Ruby to production

Path 1: Replace Threads with Fibers + Fiber.scheduler (Ruby 3+). Memory-flat scaling to tens of thousands of connections. The exercises in step 1 walk through this.

Path 2: Ractors (Ruby 3.0+) give actual parallel execution by side-stepping the GIL. Spawn a Ractor per shard of the keyspace. Trade-off: Ractor message passing is slower than Thread Mutex.

Path 3: Read redis-rb client source. You can navigate it now because you understand the wire. Look for the connection pool, the hiredis C extension, the pipelining logic.