Tag archive

#api-design

Topic-specific entry points for internal linking, discovery, and deeper subject exploration.

9 articles

gRPC vs REST: The Decision-Maker's Guide for Backend Architecture

gRPC vs REST: Which One for Your Microservices? In modern backend architecture, how services talk is as important as what they say. Choosing between REST and gRPC isn't just about syntax; it's about the trade-off between…

Apr 20, 20262 min read

ComparisonBackend Systems Mastery

#grpc#rest#api-design

System DesignBeginner

gRPC vs REST: A Decision-Maker's Guide for Backend Architecture

gRPC vs REST: Which One for Your Microservices? > Prerequisite: Before diving into protocols, ensure you understand the fundamentals of Load Balancing and API Idempotency. Choosing between REST and gRPC is one of the mos…

Apr 20, 20262 min read

ComparisonBackend Systems Mastery

#grpc#rest#api-design

System DesignAdvanced

Pagination at Scale: Keyset vs Offset

Pagination at Scale Pagination looks simple until your table has tens of millions of rows, users sort by multiple fields, and product asks for infinite scroll with strict latency SLOs. Many APIs start with LIMIT ... OFFS…

Apr 20, 20265 min read

Comparison

#api-design#pagination#performance

System DesignIntermediate

API Pagination at Scale: Why OFFSET 100,000 is a Database Killer

API Pagination at Scale: Moving Beyond OFFSET Designing a paginated API seems simple: just use LIMIT 20 OFFSET 100. This works perfectly for the first few pages. However, once your users reach page 5,000, your database p…

Apr 20, 20262 min read

Deep DiveBackend Systems Mastery

#api-design#pagination#sql

System DesignAdvanced

Distributed Transactions Part 5: The Idempotency Layer

Part 5: The Idempotency Layer In distributed systems, retries are not edge cases. They are normal behavior caused by timeouts, network partitions, broker redelivery, and process restarts. Without idempotency, each retry…

Apr 20, 20263 min read

Deep DiveDistributed Transactions Mastery

#idempotency#api-design#kafka

System DesignBeginner

gRPC Schema Evolution: Avoiding Breaking Changes

gRPC Schema Evolution gRPC contracts live longer than the services that first created them. Once multiple mobile apps, backend services, and analytics consumers depend on your protobuf messages, schema evolution becomes…

Apr 20, 20264 min read

Deep Dive

#grpc#protobuf#api-design

System DesignIntermediate

System Design: Designing Idempotent APIs for Reliable Services

System Design: Designing Idempotent APIs In a distributed system, network failures are inevitable. A common failure scenario is: "The client sends a request -> The server processes it -> The server's response fails to re…

Apr 20, 20262 min read

Deep DiveBackend Systems Mastery

#system-design#api-design#idempotency

System DesignAdvanced

Idempotency Keys in APIs: Retries, Duplicate Requests, and Exactly-Once Illusions

Any API that changes state will eventually receive the same request more than once. Mobile clients retry on flaky networks. Load balancers retry after connection resets. Users double-click. Workers crash after doing the…

Apr 7, 20267 min read

Deep Dive

#idempotency#api design#distributed systems

System DesignExpert

gRPC vs REST vs GraphQL: Choosing the Right API Protocol

API protocol selection has a longer lifespan than almost any other technical decision. REST APIs from 2010 are still running in production. gRPC services chosen for internal communication in 2018 are tightly coupled to t…

Jun 18, 20257 min read

Comparison

#grpc#rest#graphql