https://www.rambling-me.com/blog A blog to reflect my thoughts, learnings, and observations en-us me@rambling-me.com (Dopeking) me@rambling-me.com (Dopeking) Mon, 10 Aug 2026 00:00:00 GMT https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/4-correctness-in-an-async-world https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/4-correctness-in-an-async-world The hard part nobody warns you about. Once you go asynchronous and at-least-once, duplicates, retries, partial failures, and the dual-write problem all become your problem. The toolkit: idempotency as the foundation, retries with dead-letter queues, the outbox pattern for atomic publish, and sagas for multi-step flows like payment. Where a bank and a food app draw the line differently. Mon, 10 Aug 2026 00:00:00 GMT me@rambling-me.com (Dopeking) technologyscalingapi-backendidempotencyoutboxsagadead-letter-queuepractitioner https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/3-ux-of-eventual-consistency https://www.rambling-me.com/blog/posts/technology/scaling/ui-frontend/3-ux-of-eventual-consistency Where the whole pillar pays off on the client. When the backend went asynchronous, the UI could no longer promise done the instant the user acts. This is the craft of telling the truth about work in progress: optimistic updates and reconciliation, honest intermediate states, handling out-of-order and duplicate events, idempotent client actions, and error UX. And why a bank refuses the optimism a food app embraces. Sat, 22 Aug 2026 00:00:00 GMT me@rambling-me.com (Dopeking) technologyscalingui-frontendeventual-consistencyoptimistic-uiidempotencyuxpractitioner