I'm preparing for
Topic
distributed systems
60 shorts across 1 course, in learning order
🎛️ Narrow downsubject · level · topic1▾
Results · 9 for “Software design patterns”
← Front page✨ Smart search: matched by meaning, not just words
⚡ One HLD concept. 60 seconds. Interview ready
When to Use Microservices in Software Design
Microservices are useful when you need independent scaling, deployment, and clear boundaries in software design.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Managing Dependency Failures in Distributed Systems
Dependency failures can disrupt applications, but resilience patterns can help manage them.
⚡ One HLD concept. 60 seconds. Interview ready
Graceful Degradation in System Design
Graceful degradation allows apps to function partially during service failures.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Fallbacks Explained for System Design
Fallbacks allow systems to handle failures safely and maintain user experience.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Circuit Breaker Explained to Prevent Failures
A Circuit Breaker helps prevent system failures by stopping calls to unhealthy services.
⚡ One HLD concept. 60 seconds. Interview ready
Understanding Circuit Breaker: CLOSED, OPEN, and HALF-OPEN States
The Circuit Breaker pattern controls service calls to prevent failures from spreading.
⚡ One HLD concept. 60 seconds. Interview ready
Understanding Idempotency in System Design
Idempotency ensures that repeated operations in APIs do not cause duplicate effects.
⚡ One HLD concept. 60 seconds. Interview ready
Understanding Vertical and Horizontal Scaling in System Design
Vertical scaling means upgrading one server, while horizontal scaling means adding more servers.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Synchronous vs Asynchronous Communication Explained
Synchronous communication waits for a response, while asynchronous continues without waiting.
🧠Related by meaning
Not tagged “distributed systems”, but closely connected
