🔌

APIs, Networking & Integration Topics

API design, management, and integration patterns including REST, GraphQL, and other protocols. Covers API contract design, versioning strategies, error handling, idempotency, deprecation planning, and SDK/integration frameworks. Includes system-to-system integration, webhook patterns, and integration platform considerations. Excludes network infrastructure and network-layer protocols (see Network Architecture under Cloud & Infrastructure or a dedicated networking category if needed).

Enterprise Application Integration

Integration architecture across many heterogeneous enterprise systems, legacy and modern: how systems exchange data (synchronous calls, push, scheduled bulk or file transfer, messaging) and when each fits, point-to-point versus middleware designs, connectors and adapters, choosing a native connector, iPaaS or custom build, bridging SOAP/XML and REST/JSON, canonical data models and schema mapping, governing shared-schema change, system-of-record ownership, orchestration versus choreography, hybrid on-premises to cloud connectivity over outbound-only or flaky links, multi-tenant integration platforms with idempotent delivery and downstream rate limits, failure handling, dead-letter queues and reconciliation at integration seams, and phased delivery against poorly understood legacy systems. Excludes the design of a single API surface, API gateway and versioning mechanics, broker-level event streaming, data-platform ingestion, and vendor selection or cloud migration programmes covered elsewhere.

9 questions

gRPC and Service-to-Service Communication

Efficient inter-service communication using RPC-style contracts: gRPC, Protocol Buffers, and HTTP/2 transport. Covers unary and streaming modes (server, client, bidirectional), flow control, backpressure and cancellation, protobuf schema evolution and field compatibility (reserved field numbers, oneof, unknown fields), binary serialization trade-offs versus JSON/REST, deadlines and timeout propagation, status codes, retries on idempotent calls, interceptors and metadata, long-lived streams behind proxies and load balancers, gRPC-web and gateway exposure, upload and chat contract design, phased migration from REST, and choosing a transport for internal versus public-facing traffic. Excludes REST resource design, GraphQL, mTLS and mesh security, service discovery infrastructure, and broker-based messaging, which are covered elsewhere.

5 questions

API Versioning, Deprecation and Backward Compatibility

Evolving an API without breaking existing consumers: versioning schemes (URI, header, media type, semantic versioning), classifying breaking versus non-breaking changes including behavioural ones such as defaults and error text, deprecation and sunset policy and timelines (including accelerated retirement), running multiple versions concurrently, and planning consumer migrations at scale including SDK, partner, mobile and long-tail client impact. Also covers finding who still calls an old version, catching accidental breaks with contract checks in CI, expand-then-contract evolution of fields and stored data, gradual rollout with per-version monitoring, and compatibility between independently deployed services, streams and libraries. Covers compatibility guarantees across REST, GraphQL and gRPC consumers. Excludes general API surface design, payload and OpenAPI schema design, protobuf field-level mechanics, writing the notices themselves, rate limiting, gateways and database schema migration.

4 questions

API Gateways and API Management

The API gateway as a component and the API program it enforces: routing and aggregation, a policy chain for authentication hand-off, throttling hooks, request validation and transformation, protocol translation, telemetry, TLS termination, failure isolation, scaling, multi-region placement, response caching with stampede protection, tenant-aware routing and isolation, traffic steering by version or experiment cohort, and safe policy rollout and testing, plus gateway versus service mesh versus BFF placement of cross-cutting concerns. Also the management surface around it: key and credential provisioning with approval, plan and tier enforcement, separating public from partner audiences, usage analytics, and central policy governance. Excludes throttling algorithms and distributed counters, OAuth/JWT mechanics, load-balancer algorithms, documentation and developer-portal content, and whole-API-surface design.

15 questions

Rate Limiting, Throttling and Quota Management

Protecting API capacity and enforcing fair use: rate-limiting algorithms (token bucket, leaky bucket, fixed/sliding window), per-client, per-tenant and hierarchical quotas, throttling responses (429 semantics, Retry-After, limit headers), and tiered plan enforcement. Covers where to enforce limits (gateway vs. service), distributed counters, concurrency limits, client retry with backoff and jitter, and backpressure, load shedding and graceful degradation under load. Excludes gateway configuration generally, API versioning, authentication mechanics, cache design, and billing and payment pipelines.

9 questions

API Contracts and Schema Design

Defining the interface contract between producers and consumers: request/response payload shapes, data models, field-level validation, nullability, and enum/typing decisions (including safely evolving an enum's allowed values without breaking clients). Covers contract-first design with OpenAPI and JSON Schema (authoring specs, generating SDKs and mock servers, catching breaking changes in CI), mapping internal domain models to external DTOs as both evolve independently, and designing a stable error-response contract (structured error codes, correlation IDs, retryable classification). Also covers the leadership and behavioral practice of establishing and governing contract standards across teams. The contract is the durable artifact clients depend on.

5 questions

RESTful API Design

Designing resource-oriented HTTP APIs following REST constraints: resource modeling, URI structure, correct use of HTTP methods, statelessness, and HATEOAS trade-offs. Covers naming conventions, collection vs. singleton resources, filtering/sorting/pagination, and choosing appropriate status codes. The default paradigm most interview questions in this category probe.

33 questions

API Security, Authentication and Authorization

Controlling who can call an API, what they may do, and defending it against abuse. Covers the access-control mechanics: API keys, OAuth 2.0 flows, OpenID Connect, JWT issuance/validation, session vs. token auth, scopes/roles for fine-grained authorization, token lifetime and refresh, mutual TLS, and machine-to-machine vs. user-delegated access. Also covers the adversarial hardening view: input validation, injection and deserialization risks, broken object-level authorization (BOLA), mass assignment, secrets handling, and the OWASP API Security Top 10, plus securing data in transit, preventing enumeration/scraping, and testing APIs for vulnerabilities.

25 questions