#devops
4 posts
-
How Much Do You Open Up to an Outside Collaborator? Designing Isolated Dev Access Behind a BFF
The platform has exactly one door open to the internet, and every credential that touches data stays behind it. When a designer asked to run the UI locally, that collided with the design. I wrote down what to open and what to lock first, then issued an SSH key that can forward one port and nothing else.
-
Taking Caddy Out of the Deploy Path — the Structural Problem Was Touching a SPOF Automatically
Every deploy took the whole stack down for 60–100 seconds. Blue-green removed most of it, but five seconds stayed at the reverse proxy — and the real cost of those five seconds was not five seconds. It was the variance: five seconds, or indefinitely. So we took it out of the deploy path entirely.
-
[Messenger Load-Testing, Part 1] Building a Reusable Load-Test Environment — Make-based IaC, Observability, and Auth Seeding
How many TPS can a messenger's send API survive, and where exactly does it break? A 7-node mirror of production, rebuilt on demand from a single Makefile target.
-
Why You Should Never Use KeyDB as a Pub/Sub Broker for Centrifugo
KeyDB's active-replica mode looked perfect for a symmetric dual-stack chat at 100K WebSocket connections. Then I found five years of hang and deadlock issues, most still open.
