microservice
A small, independently deployed service that owns one business capability, such as billing or notifications.
In more detail
Splitting a system into microservices lets teams release independently. The cost is that every call between them crosses a network that can be slow or fail.
Example
Independent Suspense boundaries stop one slow microservice from blocking the rest of the page.Related terms
- monolith — An application built and deployed as a single unit, usually with one database.
- distributed monolith — A system split into services that still have to be released together, so it has the costs of services and none of the benefits.
- deployable — Something built and released as one unit, such as a service or a monolith.
- data ownership — The rule that each piece of data has exactly one service or team that writes it and defines what it means.
- API gateway — A server that sits in front of one or more services and handles shared concerns such as routing, authentication, rate limits and TLS for every request.
- Backend for Frontend — A small backend service built for one specific frontend, which gathers data from other services and shapes it exactly for that frontend’s screens.
- distributed tracing — Following one request across every service, queue and database it touches by recording linked spans that share a trace identifier.
- circuit breaker — A wrapper around calls to another service that stops making calls for a while after repeated failures, so the failing service can recover.
- API — A defined way for one program to ask another program to do something, such as a list of web requests a service accepts.
- backend — The server-side part of a web application that stores data and produces responses, as opposed to the frontend that runs in the browser.
- progressive loading — Showing each part of a page as soon as its own data is ready, instead of waiting for the slowest part.
- OpenAPI — A standard, language-neutral format for describing an HTTP API: its paths, operations, parameters, request and response schemas, errors and security.
- domain event — A record that something meaningful happened in the business, such as an order being created, sent so other services can react.
Taught in
- Four Hundred Missing Labels — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Serverless And Container Patterns: Where The Limits Bite — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Long-Stem Clinic: The Phrase That Decides — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Encrypting Pod-to-Pod Traffic: mTLS With Istio And Cilium — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Final Review: The Cluster You Would Defend — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Resilient Error Handling: Problem Details & Envelopes — Production Full-Stack Engineering
- API Gateway & BFF Patterns: Backend-for-Frontend — Production Full-Stack Engineering
- JWT Verification: Asymmetric Keys & Refresh Rotation — Production Full-Stack Engineering
- Distributed Tracing: OpenTelemetry & Traceparent — Production Full-Stack Engineering
- Resilience Engineering: Circuit Breakers & Retries — Production Full-Stack Engineering
- The Image Nobody Tested: Cloud Native Principles — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Architecture Sprint: The Refunds Review — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Server Components: Async Execution & Constraints — Next.js 15 & Modern App Router Architecture
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- Node.js Process Architecture: Memory & Heap Spaces — Node.js Internals & Backend Services
- Directory Traversal: Recursive Readdir & fs.watch — Node.js Internals & Backend Services
- Routing & Middleware: Path Parsing & Async Context — Node.js Internals & Backend Services
- Suspense Architecture: Promises, Fallbacks, And Co-ordination — React 19 & Modern Component Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- Exhaustive Narrowing With never In Production Handlers — Production TypeScript
- Function Utilities: ReturnType, Parameters And Constructor — Production TypeScript
- The Spine Artifact: Generating Typed Models From OpenAPI — Production TypeScript
References
- AWS: What are microservices?
- Azure Architecture Center: Microservices architecture style
- James Lewis and Martin Fowler: Microservices
- OpenTelemetry: Traces