Arpit Mishra
Fullstack AI Developer
Socials
HTTP, RPC and request/response APIs between services
The single front door for every request into your system — and the throttle that keeps one noisy client from taking the whole thing down.
How a single HTTP handshake turns into a persistent, bidirectional pipe — and what it actually takes to keep thousands of those pipes alive in production.
GraphQL trades REST's fixed endpoints for client-specified queries — solving over- and under-fetching at the cost of caching and a new backend problem: N+1.
Nouns-and-verbs versus named functions — why most 'REST' APIs are really RPC in a resource-flavored costume, and when to stop pretending.
A strongly-typed, binary RPC protocol built on HTTP/2 — why it beats REST for internal service-to-service calls, and why it struggles outside that world.
Why HTTP is stateless, why HTTP/1.1 stalls under load, and how HTTP/2 and HTTP/3 each rebuilt the transport underneath it to fix that.
