▸ Tag · #api-design
API design.
Designing APIs people can use — REST versus gRPC versus GraphQL, gateway responsibilities, rate limiting, and versioning without breaking clients.
-
ShopifyHow agentic commerce changes building on Shopify
Agentic commerce is reshaping how you build Shopify. The shift from human-centric themes to agent-ready infrastructure: Catalog, UCP, and MCP.
Read post →
-
ArchitectureREST vs gRPC: two API philosophies
The technical differences between REST and gRPC: when to use Protocol Buffers over JSON for high-performance microservices, and why good designs use both.
Read post →
-
DevOpsRate limiting vs throttling
The engineering difference between rate limiting and throttling, and how each secures your APIs and keeps infrastructure stable under heavy load.
Read post →
-
ArchitectureLoad balancer vs API gateway
Load balancers distribute traffic; API gateways enforce policy. The real differences, when to use each, and how to layer both in a production stack.
Read post →
-
ArchitectureAPI vs MCP: connecting AI systems
The core differences between traditional APIs and the Model Context Protocol (MCP) — and when to use each to build scalable, agentic AI systems.
Read post →
-
ArchitectureRate limiting: protecting your AI wallet
One runaway agent loop can mean a $5,000 LLM bill. Why request-per-second limits lie, and how hierarchical token-bucket limits protect your margins.
Read post →
-
ArchitectureAPI gateway: the front door of your AI stack
Stop exposing LLM providers to your frontend. The API gateway pattern for AI apps: tenant isolation, model aliases, rate limiting, and streaming-safe timeouts.
Read post →