Uploaded September 2026 | Updated November 2026, 3 hours ago
In this video, we explore the main inter-process communication approaches in Rust and the core coding patterns used to implement them.
We’ll cover HTTP(S), SSE, WebSocket, QUIC, TCP sockets, Unix domain sockets, stdio, and pipes, with a focus on how each communication model works and how it maps to Rust code.
Note: In this video, I sometimes use the term “protocol” broadly to refer to communication approaches or mechanisms. Strictly speaking, HTTP, QUIC, TCP, Unix sockets, stdio, and pipes are not all protocols at the same layer or abstraction level.
- 00:00 - Intro
- 00:33 - HTTP - Request/Response
- 03:39 - HTTP - SSE
- 10:47 - HTTP - WebSocket
- 15:04 - QUIC - Streams
- 18:09 - QUIC - Datagrams
- 18:48 - TCP Socket
- 22:05 - UNIX SOCKET - SOCK_STREAM
- 23:20 - UNIX SOCKET - SOCK_DGRM
- 23:57 - UNIX SOCKET - SOCK_SEQPACKET
- 24:25 - STDIO
- 25:01 - PIPES
- 25:34 - zcoder & UNIX SOCKET
Previous video on Rust Channels MPSC/SPSC used in those pseudocode ➜ youtube.com/watch?v=d_UKbQBlwOU&list=PL7r-PXl6ZPcCIOFaL7nVHXZvBmHNhrh_Q
=== Links
➜ zcoder https://zcoder.run - I am working on a very cool and unique new coding harness, (Control First, Workbench Centric, Built for parallelism) (in the Building, in Rust)
➜ Rust10x Best Practices and more ➜ rust10x.com (being redesigned)
➜ Discord general-rust - discord.gg/W2besKCzjx
➜ Twitter - twitter.com/jeremychone
➜ My current coding harness: With AIPack and pro@coder (news.aipack.ai/p/procoder-v052-demo-workbench) (Built in Rust)
➜ Discord genai & aipack - discord.gg/6KkpQBKGFS
In this video, we explore the main inter-process communication approaches in Rust and the core coding patterns used to implement them.
We’ll cover HTTP(S), SSE, WebSocket, QUIC, TCP sockets, Unix domain sockets, stdio, and pipes, with a focus on how each communication model works and how it maps to Rust code.
Note: In this video, I sometimes use the term “protocol” broadly to refer to communication approaches or mechanisms. Strictly speaking, HTTP, QUIC, TCP, Unix sockets, stdio, and pipes are not all protocols at the same layer or abstraction level.
- 00:00 - Intro
- 00:33 - HTTP - Request/Response
- 03:39 - HTTP - SSE
- 10:47 - HTTP - WebSocket
- 15:04 - QUIC - Streams
- 18:09 - QUIC - Datagrams
- 18:48 - TCP Socket
- 22:05 - UNIX SOCKET - SOCK_STREAM
- 23:20 - UNIX SOCKET - SOCK_DGRM
- 23:57 - UNIX SOCKET - SOCK_SEQPACKET
- 24:25 - STDIO
- 25:01 - PIPES
- 25:34 - zcoder & UNIX SOCKET
Previous video on Rust Channels MPSC/SPSC used in those pseudocode ➜ youtube.com/watch?v=d_UKbQBlwOU&list=PL7r-PXl6ZPcCIOFaL7nVHXZvBmHNhrh_Q
=== Links
➜ zcoder https://zcoder.run - I am working on a very cool and unique new coding harness, (Control First, Workbench Centric, Built for parallelism) (in the Building, in Rust)
➜ Rust10x Best Practices and more ➜ rust10x.com (being redesigned)
➜ Discord general-rust - discord.gg/W2besKCzjx
➜ Twitter - twitter.com/jeremychone
➜ My current coding harness: With AIPack and pro@coder (news.aipack.ai/p/procoder-v052-demo-workbench) (Built in Rust)
➜ Discord genai & aipack - discord.gg/6KkpQBKGFS










