May 29 · 5 min read · Ever tried sending a WhatsApp message while sitting in a train with zero network? Or when your phone is on airplane mode? You type the message, hit send, and it immediately pops up on your screen with
Join discussion
May 1 · 19 min read · A 200 OK response is often treated as completion. In many backend systems, it is not. It usually means one thing: the request crossed the API boundary successfully It does not always mean: the work f
Join discussionApr 17 · 3 min read · High-volume messaging exposes routing behavior, latency and execution paths most APIs don’t show. Everything works. Requests return 200.Messages get accepted.Delivery looks consistent. Until it doesn
Join discussionApr 17 · 8 min read · A team I worked with once migrated an order-placement path from gRPC to NATS because "it's decoupled and faster." The old flow was simple: the web service called PlaceOrder via gRPC, got back an order ID, rendered success to the user. The new flow: w...
Join discussionApr 5 · 17 min read · The anatomy of SMS delivery: from request to carrier Most developers think they are sending SMS through an API. They are not. They are submitting a request into a system that decides everything after
BMBridgeXAPI and 8 more commented
