Back to Blog

Weekly Commit #009

June 28, 20262 min read
... views
WeeklyCommitBackendBackgroundServiceQueueLearning

The presentation I'd been building toward finally happened, and the work week lived almost entirely in the backend.

The BETA, live

Last week I said I'd be presenting the university BETA live in front of colleagues and professors. This week I did, and the project I'd been building in a repo for months finally ran on a projector in front of a room. I decided to record a video showcasing the web and mobile app, both running on the same backend. Everything held and the presentation went well.

Serializing address changes at work

On the professional side the week was heavier and lived mostly in the backend. The task: address changes were being propagated to an external system in parallel, and the volume was overloading it. The fix was to stop firing those calls concurrently and serialize them instead, so I built a background service with a single consumer that pulls work off a queue and processes one address at a time.

The details that took the time

That sounds simple until you get into the details. The submission now shows an "in integration" state in the audit history, transitions to "accepted" once the external system confirms, and logs failures cleanly instead of swallowing them. The least visible part took the most time: the original user's identity has to be carried through to the background thread, or the save fails on a database constraint.

#WeeklyCommit #Backend #BackgroundService #Queue

Follow along here or on LinkedIn where I'll be sharing each new commit.