@abhishekshr
Nothing here yet.
Nothing here yet.
49m ago · 5 min read · In Part 7, I taught my server how to die gracefully. It felt production-ready. Auth, rate limiting, caching, clean shutdown — the API was doing real work. I said Part 8 would be "Docker + Postgres." I was wrong. Postgres alone deserved its own post...
Join discussion1d 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 · 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 · 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 · 5 min read · In Part 3, I built authentication — JWT tokens, bcrypt hashing, middleware that wraps handlers like Russian dolls. The API had four endpoints and was fully protected. But it could only create and read entries. No updating. No deleting. And zero tests...
Join discussion