Skip to content
tezvyn:
Menu

Microservices

51 bites tagged Microservices: interview questions with model answers, and 60-second explainers.

Test yourself: Top 30 Microservices interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.
Node.js & Express1 min read

Session-based versus token-based authentication

Sessions store server-side state with a cookie id, tokens carry self-contained claims with no server store, weigh revocation versus scalability, especially across services.

Monitoring & SRE1 min read

Canary a shared downstream microservice

Route a slice of traffic to the canary via mesh rules, propagate context, and use distributed tracing to measure impact on upstream callers across the full path.

Monitoring & SRE2 min read

Trace context and propagation across services

Trace context bundles trace ID, span ID, and flags; propagated via headers like W3C traceparent so each service extracts and continues the trace.

Monitoring & SRE1 min read

How does distributed tracing work?

Trace ID ties one request together, span IDs are individual operations, context propagates via headers.

Monitoring & SRE2 min read

Error budget policy across dependent microservices?

Set per-service SLOs but anchor on user-facing journey SLOs, budget for dependency error via the multiplication of availabilities, attribute downstream-caused failures correctly, and use…

MLOps & Infrastructure1 min read

CI/CD for microservice-based ML systems

Independent per-service pipelines, contract testing to protect interfaces and schemas, and incremental deploys (canary, blue-green); manage data and model contracts, not just code.

Databases & Architecture1 min read

Why choose Kafka over a REST endpoint for ingestion

Kafka buffers spikes, decouples producers from consumers, replays and fans out durably.

Databases & Architecture1 min read

How do you keep consistency without multi-document transactions?

A Saga runs a sequence of local transactions, each with a compensating action to undo on failure, coordinated via choreography or orchestration.

Cloud Platforms1 min read

Explain the Strangler Fig pattern

A facade routes traffic, new services gradually replace legacy features one slice at a time, and the old system is retired when fully strangled.

Cloud Platforms2 min read

Centralized logging across microservices

Ship structured logs from every service into a central searchable store, then propagate a correlation ID through all hops to trace one request.

Cloud Platforms1 min read

Dynamic database credential rotation for microservices

A secrets manager issues short-lived per-service credentials, services authenticate by workload identity and fetch or refresh secrets without restart, leases expire and rotate automatically.

Go & Rust2 min read

Using context.Context across microservice calls in Go

Context carries cancellation, deadlines, and values; pass ctx as first arg, set one WithTimeout at the edge, attach a request ID via WithValue, thread it through downstream calls so all cancel…

Docker & Kubernetes1 min read

What is distributed tracing in microservices?

A trace is a tree of spans tied by trace and span IDs, propagated via headers like W3C traceparent.

React & Next.js2 min read

Vercel Ship 2026: agent stack, eve framework, and microservices

Vercel Ship 2026 unveils open-source eve framework and Vercel Services for microservices July 1. Vercel is repositioning as agentic infrastructure with Connect credentials and expanded Python backends. Evaluate if your next agent deploys here instead of AWS.

Product Strategy2 min read

How does product strategy influence architectural decisions? Provide a specific example.

This tests if you tie architecture to product outcomes like iteration speed. A strong answer picks patterns by company stage, cites a concrete tradeoff, and treats reliability as a product feature.

Product Strategy2 min read

Propose a long-term strategy to decompose a monolith while maintaining API stability

This tests strategic prioritization and incremental migration without ecosystem breakage. Start with simple decoupled capability, go macro first then micro, split vertically by domain owning data, and use atomic steps with facades to preserve APIs.

Product Strategy2 min read

Design quantifiable proxy metrics for a microservices velocity claim

Use DORA velocity and stability metrics plus leading indicators like build and PR cycle time.

Product Strategy2 min read

Propose a scalable entitlement architecture for complex rules

Tests separation of hot-path reads from async policy work. Great answers: edge-cache plan tokens; stream quota usage async; isolate rules in a microservice. Red flag: doing a DB lookup or sync quota check per request.

Product Strategy2 min read

How would you leverage microservices to out-maneuver a monolithic competitor?

Tests turning architecture into product velocity. Exploit competitor's release cycle with independent service teams shipping features in days not months via domain boundaries. Red flag: seeing microservices as purely technical or suggesting big-bang rewrite.

Product Strategy2 min read

How would you architect a system for rapid experimentation and validation?

Tests designing decoupled experimentation infrastructure that scales past 1M users. Strong answers split assignment, flags, metrics, and analysis into independent event-driven services with change data capture isolating production.

Product Strategy2 min read

How do you frame monolith vs microservices trade-offs under market uncertainty?

Connecting architecture to business strategy under uncertainty. Strong answers say monoliths offer cheap optionality when markets are unknown, but winner-take-all makes speed existential; microservices are a post-PMF scaling tax.

Growth & Experimentation2 min read

Design a highly available entitlements service with caching

This tests balancing read performance with consistency in access control. A strong answer proposes tiered caching with proactive invalidation, read-optimized hot paths, and event-sourced temporary grants.

Content & Copywriting2 min read

How do you fulfill a GDPR erasure request across microservices?

Log the request, emit a durable erasure event, let each service delete or anonymize locally, then reconcile.

Content & Copywriting2 min read

Design a centralized Copy Service with versioning, segmentation, and experiments

This tests separation of editorial workflow from runtime delivery. A strong answer covers immutable versioned records, a resolution API evaluating segmentation rules, and delegating experiment bucketing externally.

Get Microservices bites daily.

Five a day, five minutes, offline. With quizzes so it sticks.

The iPhone app is on the way

We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.

Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.

Get it on Google PlayiPhone app coming soon