https://212clab.pages.dev/en/project/Recent content in Project on blog.212clabHugoenFri, 01 May 2026 00:00:00 +0000https://212clab.pages.dev/en/project/playball/Fri, 01 May 2026 00:00:00 +0000https://212clab.pages.dev/en/project/playball/<table> <thead> <tr> <th>Item</th> <th>Details</th> </tr> </thead> <tbody> <tr> <td><strong>Period</strong></td> <td>2026.01 ~ 2026.04</td> </tr> <tr> <td><strong>Type</strong></td> <td>Team Project (KTCloud TechUp Alliance)</td> </tr> <tr> <td><strong>Team size</strong></td> <td>16 members</td> </tr> <tr> <td><strong>Role</strong></td> <td>DevOps / Infrastructure Engineer</td> </tr> <tr> <td><strong>Service</strong></td> <td><a href="https://playball.one">playball.one</a></td> </tr> <tr> <td><strong>GitHub</strong></td> <td><a href="https://github.com/212clab/330-playball-infra">330-playball-infra</a></td> </tr> <tr> <td><strong>Slides</strong></td> <td><a href="https://drive.google.com/file/d/1rKzKeAB9tI6TFs3Nn6q-Tsc2rfzjcL-Z/view?usp=sharing">Presentation Deck (Google Drive)</a></td> </tr> <tr> <td><strong>Troubleshooting</strong></td> <td><a href="https://212clab.pages.dev/en/troubleshooting/?project=330-playball-infra">Full list</a></td> </tr> </tbody> </table> <hr> <h2 id="project-overview">Project Overview</h2> <p>I designed and operated the full infrastructure for PlayBall, a baseball ticket booking platform. The infrastructure was shaped around five key requirements: fast dev environment setup, cost efficiency, operational observability, security, and handling traffic spikes.</p>https://212clab.pages.dev/en/project/protocol-deep-dive/Fri, 01 May 2026 00:00:00 +0000https://212clab.pages.dev/en/project/protocol-deep-dive/<table> <thead> <tr> <th>Item</th> <th>Details</th> </tr> </thead> <tbody> <tr> <td><strong>Period</strong></td> <td>2026.05 ~ (in progress)</td> </tr> <tr> <td><strong>Type</strong></td> <td>Personal learning project</td> </tr> <tr> <td><strong>Language</strong></td> <td>Go</td> </tr> <tr> <td><strong>GitHub</strong></td> <td><a href="https://github.com/212clab/315-protocol-deep-dive">315-protocol-deep-dive</a></td> </tr> </tbody> </table> <hr> <h2 id="project-overview">Project Overview</h2> <p>A project to implement the inner workings of network protocols directly in code, and compare differences across layers through benchmarks. Questions like &ldquo;why is gRPC faster?&rdquo; and &ldquo;how different are TCP and UDP in practice?&rdquo; are answered through direct measurement.</p> <hr> <h2 id="protocols-compared">Protocols Compared</h2> <table> <thead> <tr> <th>Layer</th> <th>Protocol</th> <th>Key Characteristics</th> </tr> </thead> <tbody> <tr> <td><strong>L3</strong></td> <td>ICMP</td> <td>No handshake, raw ICMP header, TTL</td> </tr> <tr> <td><strong>L4</strong></td> <td>TCP</td> <td>3-way handshake, ordered delivery, flow control</td> </tr> <tr> <td><strong>L4</strong></td> <td>UDP</td> <td>Connectionless, unordered, packet loss possible</td> </tr> <tr> <td><strong>L7</strong></td> <td>HTTP/1.1</td> <td>Text headers, 1 request per connection vs keep-alive</td> </tr> <tr> <td><strong>L7</strong></td> <td>HTTP/2</td> <td>TLS+ALPN, multiplexing, HPACK header compression</td> </tr> <tr> <td><strong>L7</strong></td> <td>gRPC</td> <td>Protobuf over HTTP/2, Unary/ServerStream/Bidi</td> </tr> <tr> <td><strong>L7</strong></td> <td>gRPC-Web</td> <td>gRPC from the browser via HTTP/1.1 proxy</td> </tr> </tbody> </table> <hr> <h2 id="structure">Structure</h2> <pre tabindex="0"><code>├── l3/icmp/ ICMP ping ├── l4/tcp/ TCP echo server/client ├── l4/udp/ UDP echo server/client ├── l7/http1/ HTTP/1.1 server/client ├── l7/http2/ HTTP/2+TLS server/client ├── l7/grpc/ gRPC server/client + proto ├── l7/grpcweb/ gRPC-Web proxy + browser demo ├── benchmark/ Full protocol benchmark suite ├── dashboard/ Chart.js web dashboard └── cmd/ CLI entrypoints </code></pre><p>Each protocol is implemented as a server/client pair, benchmarked with the same payload to compare latency, throughput, and overhead.</p>