Skip to content

Microservices Architecture: Interview Prep Guide

Goal: Broad, systematic coverage โ€” from design thinking to production deployment. Built for senior developers moving into architecture roles.


The Mental Model: Design โ†’ Build โ†’ Run

graph LR
    A[Foundations] --> B[DDD]
    B --> C[Patterns]
    C --> D[Events]
    D --> E[APIs]
    E --> F[Resilience]
    F --> G[Observability]
    G --> H[Security]
    H --> I[Deployment]
    I --> J[Interview]

flowchart LR
    subgraph DG["DESIGN โ€” where are the boundaries?"]
        D1["DDD ยท bounded contexts<br/>CAP ยท ACID vs BASE"]
    end
    subgraph BD["BUILD โ€” how do services interact?"]
        B1["patterns ยท sagas ยท outbox<br/>REST / gRPC / events"]
    end
    subgraph RN["RUN โ€” how does it stay alive?"]
        R1["resilience ยท observability<br/>security ยท K8s ยท GitOps"]
    end
    DG --> BD --> RN
    RN -.->|"incidents & learning<br/>feed back"| DG

Sections at a Glance

# Section Core Topics
01 Architectural Foundations Styles, CAP, Conway's Law, Hexagonal, Onion, Clean
02 Domain-Driven Design Bounded Contexts, Aggregates, Context Mapping, Ubiquitous Language
03 Microservices Patterns Decomposition, Integration, Service Discovery, Caching, Sidecar, Outbox
04 Event-Driven Architecture Kafka, CQRS, Event Sourcing, Saga, Messaging Patterns, DLQ
05 API & Communication REST, gRPC, GraphQL, API Gateway, BFF, Versioning, Configuration
06 Resilience & Reliability Circuit Breaker, Retry, Bulkhead, Timeout, Rate Limiting, Chaos
07 Observability Logs, Metrics, Traces, SLO, OpenTelemetry, DORA Metrics
08 Security OAuth2, JWT, mTLS, Secrets, Zero Trust, Testing Strategies
09 Deployment & Infrastructure Kubernetes, Helm, GitOps, Blue-Green, Canary, Configuration
10 Interview Prep Design scenarios, Trade-offs, ADRs, Spring Boot map

  1. Sections 01โ€“02 โ€” Architecture thinking + DDD (the why behind service boundaries)
  2. Sections 03โ€“04 โ€” Patterns + events (the how of building distributed systems)
  3. Sections 05โ€“09 โ€” Verify and fill gaps in what you already know
  4. Section 10 โ€” Final synthesis through the interview lens

What Architecture Interviews Actually Test

  • Can you decompose a system into coherent services? (DDD)
  • Do you understand distributed system trade-offs? (CAP, eventual consistency)
  • Can you reason about failure scenarios? (Resilience patterns)
  • Do you know how to observe a running system? (Observability)
  • Can you articulate why you'd choose one pattern over another?

Breadth first, depth on demand

This guide is intentionally wide. If a concept feels shallow, that's your signal to go deeper on that specific topic after building the mental map.


๐Ÿ“ Knowledge Check

#

Question 1

The guide's mental model is Design โ†’ Build โ†’ Run. Where do DDD, sagas, and observability each fit โ€” and why does the order matter?

#

Question 2

'Architecture interviews test trade-offs, not trivia' โ€” which answer demonstrates the right instinct: 'microservices are better' or 'it depends, here's when each wins'?

#

Question 3

'Breadth first, depth on demand' โ€” in a system-design interview where you're asked to design notifications at scale, which 2-3 topics from this guide would you reach for first, and why?