The stuff cron jobs just can't do.After fixing the history limit problem (Part 1, Part 2), I had a working ETL. But while I was in the codebase, I added three more patterns that I couldn't stop thinking about. None of them are possiblMay 12 · 5 min readshubham18.hashnode.dev
Two lines of code that made my ETL unkillable.In Part 1 I showed how a Temporal workflow silently dies when it hits the 50,000 event history limit. A creator backfill triggered it. No error, no alert, 4 days of missing data. This part is the fix.May 12 · 4 min readshubham18.hashnode.dev
My background job silently died. I had no idea for days.I was building an Instagram analytics platform. Every 15 minutes, a job runs — fetch posts, pull metrics, store everything. For most creators it worked fine. Then one creator ran a backfill. Two yearsMay 12 · 3 min readshubham18.hashnode.dev
How We Seamlessly Integrated WordPress into Our Next.js App for a Scalable Blog SolutionAt our company, we recently faced a challenge that many dev teams encounter:We wanted to introduce a fully-featured blog into our existing Next.js + Node.js application, but building everything from scratch — post management, SEO optimization, editor...Jul 28, 2025 · 3 min readshubham18.hashnode.dev
AWS MediaConvert with Merge Video SegmentsA step‑by‑step guide to build a Temporal activity that: Uploads video segments & audio to S3 Concatenates the video segments (no audio) Overlays the voice‑over track Polls for completion and returns the final S3 URL Prerequisites Node.js >= 2...Jul 10, 2025 · 3 min readshubham18.hashnode.dev