Docs Overview

Homepage

Server Runtime

RESP Protocol

Storage Model

This docs area now maps redis-rs by implementation boundary instead of collapsing the codebase into a few broad summaries.

Each main chapter is written to answer the same concrete questions:

• which file owns this behavior
• which function is the entrypoint
• what happens first, next, and last
• what data structure is being passed through
• which shortcut or limitation matters if you extend the code

Reading path

Use this sequence if you want to understand the implementation from the outside in:

1. runtime entry and shared server state
2. RESP parsing and encoding
3. string storage and stream containers
4. RDB snapshot parsing
5. replication handshake and fan-out
6. command dispatch
7. streams and transaction replay

Chapters

• Server Runtime
  • src/main.rs
  • src/server.rs
  • src/options.rs
• RESP Protocol
  • src/protocol.rs
• Storage Model
  • src/storage.rs
  • src/server.rs
  • src/cmd.rs
• RDB Parser
  • src/rdb.rs
• Replication Flow
  • src/main.rs
  • src/replication_client.rs
  • src/server.rs
  • src/cmd.rs
• Command Execution
  • src/cmd.rs
  • src/server.rs
  • src/protocol.rs
• Streams and Transactions
  • src/cmd.rs
  • src/server.rs
  • src/storage.rs

What changed from the earlier docs split

The repository is compact, but it still has more than three real implementation boundaries:

• entry/runtime orchestration
• RESP parsing
• storage
• RDB decoding
• replication handshake and fan-out
• command dispatch
• stream and transaction extensions

The newer split keeps those boundaries visible and also documents current behavior accurately, including places where the implementation is intentionally narrower than production Redis.