Start with the wire format
The source implements RESP response helpers for simple strings, errors, integers, bulk strings, and arrays. Its request parser handles arrays of bulk strings, including incremental input where a complete request has not arrived yet.
The in-memory model separates strings, hashes, and sets. Supported command cases include SET, GET, hash operations, set operations, PING, QUIT, and BGSAVE. The code also defines dump and append-only persistence filenames.
Keep compatibility claims narrow
A small command subset can be useful for learning how a familiar client protocol fits together. It should not be described as a full Redis replacement, a time-series database, or equivalent to Redis durability and replication.
The default listener is loopback. That fits an experiment intended for controlled local use rather than a public data service. The current hosted V39 platform's production Redis setup is a separate implementation and operating boundary.
Make framing inspectable
Seeing the request bytes beside the interpreted command makes protocol behavior easier to debug. A command's successful response is only one layer: partial input, invalid lengths, connection boundaries, and recovery after interruption also shape correctness. The small implementation keeps those mechanics close enough together to study without mistaking its subset for full Redis compatibility.