General · Learning hub

Microservices cheat sheet & developer notes

Microservices cheat sheet and 2 curated developer notes — core concepts, patterns, and interview prep. Maintained by the DevRecall team.

Save this stack to your DevRecall Test yourself — Microservices quiz More General notes

01 · Microservices

Microservices Interview Questions

Microservices Interview Questions. Monolith vs microservices trade-offs? Monolith: simpler dev/deploy, one DB, lower latency. Micro: independent scaling/deploy, tech diversity, team autonomy — but distributed systems com…

02 · Microservices

Microservices Architecture

Microservices Architecture. Core Principles. Single Responsibility — each service owns one bounded context (e.g., Users, Orders, Inventory). Decentralized data — each service has its own database; no shared DB between se…

From the community

Notes from developers

See all in General →

TypeScriptgeneral

Interview Questions

TypeScript Interview Questions. Comprehensive TypeScript interview questions covering type system, generics, utility types, and best practices:. Fundamentals. 1. What is TypeScript?. TypeScript is a…

TypeScriptgeneral

Advanced Types (Generics & Utility Types)

TypeScript Advanced Types. Generics. // Generic function function identity<T>(arg: T): T { return arg; } const num = identity<number>(42); // Explicit const str = identity('hello'); // Inferred //…

Concepts to know for Microservices

Load Balancing: L4 vs L7, Algorithms, Health ChecksWhat L4 and L7 balancers actually forward, why least-request beats round robin, how health checks and draining make deploys safe, and why gRPC breaks it.Intermediate·13 min CAP Theorem in PracticeWhat CAP really constrains (only behaviour during a partition), why "pick two" is wrong, and how PACELC, quorums and consistency models become design choices.Intermediate·14 min Event Sourcing and CQRSStoring state as an append-only log of events, rebuilding it by replay, and serving reads from separate projections, plus the costs: versioning and stale reads.Advanced·15 min The Transactional Outbox PatternWhy saving to the database and publishing an event can never be atomic, how an outbox table plus a relay fixes it, and what ordering and duplicates still cost.Intermediate·13 min Observability: Logs, Metrics and TracesWhat logs, metrics and traces each answer, why label cardinality breaks metrics, how a trace ID crosses services, and how SLOs turn signals into alerts.Intermediate·15 min

Related stacks

API Design Agile Agile Methodology Algorithms Apache Authentication & Authorization C C++CI/CD Best Practices CQRS CUDA Caching Strategies

Browse all stacks →

Keep your Microservices knowledge sharp.

Save this stack to your personal DevRecall — add your own notes, track what you're learning, and share what you know with the community.

Get started — free forever