---
title: "Ali Asgar (@amkantawala) | Hashnode"
description: "Scaling systems. Sharing lessons. Read the latest articles by Ali Asgar on Hashnode."
url: "https://hashnode.com/@amkantawala"
---

@amkantawala

# Ali Asgar

@amkantawala · Chennai, India · Joined June 2026

Scaling systems. Sharing lessons.

### [How I'd Design a Kafka-Based Payment Event Pipeline from Scratch](https://aliasgarmkantawala.hashnode.dev/how-i-d-design-a-kafka-based-payment-event-pipeline-from-scratch?utm_source=hashnode&utm_medium=feed)

Architecture walkthroughs tend to show you the polished version — the diagram that survived a whiteboard, cleaned up after the fact. What they skip is the sequence of decisions, tradeoffs, and dead en

4 min read · [aliasgarmkantawala.hashnode.dev](https://aliasgarmkantawala.hashnode.dev/how-i-d-design-a-kafka-based-payment-event-pipeline-from-scratch?utm_source=hashnode&utm_medium=feed)

[Jul 16](https://hashnode.com/posts/how-i-d-design-a-kafka-based-payment-event-pipeline-from-scratch/6a595d3774127f4ec58d0c0b)

### [Exactly-Once Semantics in Kafka: Promise vs. Reality](https://aliasgarmkantawala.hashnode.dev/exactly-once-semantics-in-kafka-promise-vs-reality?utm_source=hashnode&utm_medium=feed)

"We're using Kafka with exactly-once semantics, so we don't have to worry about duplicates." I've heard this in architecture reviews, design docs, and postmortem explanations. It represents a misunder

4 min read · [aliasgarmkantawala.hashnode.dev](https://aliasgarmkantawala.hashnode.dev/exactly-once-semantics-in-kafka-promise-vs-reality?utm_source=hashnode&utm_medium=feed)

[Jul 15](https://hashnode.com/posts/exactly-once-semantics-in-kafka-promise-vs-reality/6a57fb12a4f6524cc10b8e15)

### [The Difference Between Retry and Idempotency, They're Not the Same](https://aliasgarmkantawala.hashnode.dev/the-difference-between-retry-and-idempotency-they-re-not-the-same?utm_source=hashnode&utm_medium=feed)

Let me start with the confusion that prompted this post: in a recent mentoring session, a senior engineer described their payment service as "idempotent" because it had exponential backoff on retries.

4 min read · [aliasgarmkantawala.hashnode.dev](https://aliasgarmkantawala.hashnode.dev/the-difference-between-retry-and-idempotency-they-re-not-the-same?utm_source=hashnode&utm_medium=feed)

[Jul 6](https://hashnode.com/posts/the-difference-between-retry-and-idempotency-they-re-not-the-same/6a4b0b140769fd795a28fc32)

### [Idempotency in Payment APIs — Not Optional, Not Later](https://aliasgarmkantawala.hashnode.dev/idempotency-in-payment-apis-not-optional-not-later?utm_source=hashnode&utm_medium=feed)

There's a version of this story that plays out at almost every fintech startup I've worked with: the team ships a payment API, it works in testing, it goes live. Then a user's connection drops mid-req

4 min read · [aliasgarmkantawala.hashnode.dev](https://aliasgarmkantawala.hashnode.dev/idempotency-in-payment-apis-not-optional-not-later?utm_source=hashnode&utm_medium=feed)

[Jul 2](https://hashnode.com/posts/idempotency-in-payment-apis-not-optional-not-later/6a46c44002982991ee7ce80b)

### [Eventual Consistency Is Misunderstood by Most Engineers](https://aliasgarmkantawala.hashnode.dev/eventual-consistency-is-misunderstood-by-most-engineers?utm_source=hashnode&utm_medium=feed)

I've interviewed dozens of engineers at the senior level. When I ask them to explain eventual consistency, most recite the textbook answer: "data will converge to a consistent state — eventually." Wha

5 min read · [aliasgarmkantawala.hashnode.dev](https://aliasgarmkantawala.hashnode.dev/eventual-consistency-is-misunderstood-by-most-engineers?utm_source=hashnode&utm_medium=feed)

[Jun 29](https://hashnode.com/posts/eventual-consistency-is-misunderstood-by-most-engineers/6a42e12b75059965f288d5fe)
