2d ago · 4 min read · In Part 6, I added rate limiting and Redis. The API was getting real — pagination, caching, authentication, rate limiting. It handled traffic. It scaled horizontally. Then I pressed Ctrl+C and realized something: every request in flight just vanished...
Join discussion2d ago · 3 min read · I run a LinkedIn employees scraper on Apify that had a 62% false positive problem. Here is how we fixed it. The false positive problem The first version was a Google dork. Query site:linkedin.com/in/ "TargetCompany" and parse the SERP. Fast, cheap, a...
Join discussion2d ago · 12 min read · Originally published on rollgate.io/blog/feature-flags-golang. Why Feature Flags in Go? Go is the language of choice for microservices, API backends, CLI tools, and infrastructure software. Teams shipping Go code in production face the same challeng...
Join discussion
3d ago · 4 min read · In Part 5, I added pagination and in-memory caching. Both worked fine — until I thought about what happens with more than one server. Three days, two rewrites, one lesson: in-memory is a local solution to a global problem. Day 18: Rate Limiting From ...
Join discussion3d ago · 11 min read · diskdoc and dockit: same problem, two languages, different answers I built two tools that clean up disk space. Both are CLIs. Both deal with Docker. Both ship as a single binary. And if you put them side by side, they look like the same project in tw...
Join discussion3d ago · 15 min read · Originally published at recca0120.github.io terraform validate checks syntax. terraform plan previews changes. Neither tells you whether the infrastructure you deploy actually works. Terratest fills that gap by deploying real infrastructure, running ...
Join discussion4d ago · 3 min read · In Part 4, I finished full CRUD and wrote my first Go tests. The API worked — but I was the only user, hitting it from my terminal with 10 test entries. Then I asked: what happens when there are 10,000 rows? Two days, two features. Both taught me thi...
Join discussion4d ago · 9 min read · gRPC interceptors are the middleware pattern, specialized for gRPC. If you've written HTTP middleware before, the shape is familiar — a function that wraps a call, can observe or modify the request, pass to the next handler, then observe or modify th...
Join discussion
