I'm preparing for
Topic
system design
66 shorts across 1 course, in learning order
🎛️ Narrow downsubject · level · topic2▾
Results · 17 for “Basic software engineering principles”
← Front page✨ Smart search: matched by meaning, not just words

⚡ One HLD concept. 60 seconds. Interview ready
Understanding Functional and Non-Functional Requirements
Functional requirements define what a system does, while non-functional requirements define how it performs.

⚡ One HLD concept. 60 seconds. Interview ready
Understanding High-Level Design (HLD) and Low-Level Design (LLD)
HLD provides an overview of system architecture, while LLD details implementation specifics.

⚡ One HLD concept. 60 seconds. Interview ready
HLD: Search Engine Architecture and Its Components
Search engines collect, index, retrieve, and rank documents to provide relevant results.

⚡ 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
Understanding the Bulkhead Pattern in System Design
The Bulkhead Pattern isolates resources to protect critical workloads from failures.

⚡ One HLD concept. 60 seconds. Interview ready
Choosing Service Boundaries in Microservices Architecture
Choosing the right boundaries for microservices is crucial for effective architecture.

⚡ One HLD concept. 60 seconds. Interview ready
Monolith vs Microservices: Choosing the Right Architecture
Monolithic and microservices architectures each have unique advantages and challenges for software development.

⚡ One HLD concept. 60 seconds. Interview ready
Understanding Alerting in High-Level Design
Alerting helps notify the right people about production issues quickly.

⚡ One HLD concept. 60 seconds. Interview ready
HLD: Understanding REST, RPC, and gRPC Differences
REST, RPC, and gRPC are different methods for communication in software systems.

⚡ One HLD concept. 60 seconds. Interview ready
HLD: 5 Microservices Communication Patterns Explained
Microservices can communicate using five key patterns based on their needs.

⚡ One HLD concept. 60 seconds. Interview ready
Understanding Availability vs Reliability in System Design
Availability is about access; reliability is about correct performance.

⚡ One HLD concept. 60 seconds. Interview ready
HLD: Microservices vs Modular Monolith Explained
Microservices and modular monoliths differ mainly in deployment and communication methods.

⚡ 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
Understanding the USE Method for Infrastructure Bottlenecks
The USE Method helps find and analyze infrastructure bottlenecks in software systems.

⚡ One HLD concept. 60 seconds. Interview ready
Understanding Database per Service in Microservices Architecture
Database per Service ensures each microservice owns its data, reducing dependencies.

⚡ 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
API Gateway vs Proxy vs Load Balancer: Key Differences
API Gateway, Proxy, and Load Balancer serve different roles in managing requests and traffic in systems.
🧠Related by meaning
Not tagged “system design”, but closely connected

