API Learning Roadmap
API learning roadmap covering protocols, design, auth, observability, and change.
APIs, HTTP, browser constraints, and backend interface patterns that shape how web systems exchange data, handle change, and fail in production.
API learning roadmap covering protocols, design, auth, observability, and change.
REST API concepts, constraints, and HTTP patterns in one reference sheet.
GraphQL lets clients request exact API fields through a typed schema.
REST and GraphQL compared through interface shape, flexibility, and tradeoffs.
Nine API test types and the failure modes each one is meant to catch.
gRPC uses Protobuf contracts and HTTP/2 for efficient service calls.
API gateway responsibilities for request admission, routing, and cross-cutting policy.
Secure web API access through authentication, authorisation, and abuse controls.
API pagination through stable ordering, offsets, cursors, and page tokens.
Polling and webhooks compared by freshness, infrastructure needs, and failure handling.
HTTP transport evolution through multiplexing, QUIC, and reduced blocking.
Forward and reverse proxies compared by traffic direction, control, and purpose.
Load balancers route requests across healthy servers and absorb backend failure.
HTTP methods and their safety, idempotency, and resource update semantics.
Secure API design through authentication, authorisation, validation, and rate limits.
API boundaries versus SDK tooling for integration contracts and developer ergonomics.
URL, URI, and URN differences through naming, location, and identifier scope.
Core production web application components from clients and APIs to data stores.
Traffic delivery models for unicast, broadcast, multicast, and anycast.
URL components for resource addressing, routing, caching, and security rules.
Version numbers signal compatibility, release scope, and upgrade risk.
API gateway roles in edge routing, cross-cutting policy, and protocol mediation.
API gateways for routing, authentication, rate limiting, and edge policy enforcement.
API design patterns for resources, errors, versioning, and operational guarantees.
Four GraphQL adoption patterns, from API wrappers to federated ownership.
GraphQL query execution, resolver fan-out, and schema control at LinkedIn.
Load balancers and API gateways compared by routing, policy, and edge control.
Reverse proxies, API gateways, and load balancers compared by responsibility.
Eight API design tips covering resources, versioning, errors, and request efficiency.
JavaScript execution with the call stack, heap, event loop, and async tasks.
Network types compared by scope, ownership, and transport distance.
Eighteen common network ports and the protocols and services they expose.
Load balancer use cases through traffic distribution, failover, and rollouts.
CSS applies layout and visual rules to structured HTML content in the browser.
HTTP/2 speeds up web traffic with multiplexing, header compression, and reuse.
Browser rendering through parsing, style calculation, layout, paint, and compositing.
Internet routing policies through BGP attributes, peering, and transit.
HTTP headers that control caching, content handling, and proxy behaviour.
NAT address translation through private networks, port mapping, and shared public IPv4.
gRPC calls over HTTP/2 with Protocol Buffers, streams, and generated stubs.
Five unusual HTTP status codes and the protocol edge cases behind them.
Load balancer roles in health checks, routing, traffic control, and safe rollouts.
Short polling, long polling, SSE, and WebSockets for browser update delivery.