Talking to Redis With Just Netcat

A Redis client is not magic. It opens a TCP socket on port 6379, encodes your command as bytes, sends them, and reads bytes back. That's it. In this video we throw away the client and talk to Redis ourselves using netcat — so you actually see the bytes on the wire.

We install Redis three ways (Mac, Linux, Docker), open a raw TCP connection with `nc`, send a PING by hand, then send SET and GET in proper RESP format. By the end you'll know what every Redis client in every language is doing under the hood — and the RESP protocol will stop feeling like a black box.

This is video 2 of "Redis End to End" — a series that builds Redis intuition from first principles, no hand-waving.

🧠 What you'll walk away with
- How to install and start Redis on any machine
- The three things every Redis client does (open socket → encode bytes → read bytes)
- RESP protocol — Simple Strings, Errors, Integers, Bulk Strings, Arrays

🔗 Resources
- RESP spec — https://redis.io/docs/latest/develop/reference/protocol-spec/
- Redis download — https://redis.io/download
- Docker image — https://hub.docker.com/_/redis
- Series playlist — https://www.youtube.com/playlist?list=PLC4dBtMbzLJ_zGFoTpfOUZvKV-DAZo_aR
- Notes & diagrams (Obsidian vault) — obsidian://open?vault=Redis-YT-Series&file=youtube%2Fredis-notes

Tags
----------
redis,redis tutorial,redis for beginners,install redis,redis install mac,redis install ubuntu,redis docker,redis without client,redis resp protocol,resp protocol,redis netcat,redis raw tcp,redis port 6379,redis client internals,how redis works,redis under the hood,redis from scratch,redis explained,redis basics,redis crash course,backend engineering,system design,databases,in memory database,redis end to end

#redis #backend #systemdesign #databases

Видео Talking to Redis With Just Netcat канала Yatharth Verma