I'm preparing for
Topic
system design
116 shorts across 1 course, in learning order
🎛️ Narrow downsubject · level · topic2▾
Results · 22 for “Software Architecture”
← Front page✨ Smart search: matched by meaning, not just words
⚡ 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
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
What FAANG Interviewers Evaluate in System Design Interviews
FAANG interviewers evaluate problem understanding, architecture, scalability, and communication skills.
⚡ One HLD concept. 60 seconds. Interview ready
REST API Design: Building Scalable APIs for Real-World Use
REST API design focuses on creating clean, efficient, and scalable web services.
⚡ 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
API Gateway: The Front Door of Your System
An API Gateway simplifies client access to backend services in microservices.
⚡ 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
Choosing Service Boundaries in Microservices Architecture
Choosing the right boundaries for microservices is crucial for effective architecture.
⚡ 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: 5 Microservices Communication Patterns Explained
Microservices can communicate using five key patterns based on their needs.
⚡ 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
Graceful Degradation in System Design
Graceful degradation allows apps to function partially during service failures.
⚡ One HLD concept. 60 seconds. Interview ready
Understanding the Saga Pattern in Distributed Transactions
The Saga Pattern manages distributed transactions using local transactions and compensating actions.
⚡ One HLD concept. 60 seconds. Interview ready
Understanding SLIs, SLOs, and SLAs in Reliability Engineering
SLIs measure service performance, SLOs set reliability targets, and SLAs are customer agreements.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Fail Fast vs Fail Safe in System Design
Fail Fast means stopping quickly on errors, while Fail Safe ensures safety in failures.
⚡ One HLD concept. 60 seconds. Interview ready
SQL vs NoSQL: Choosing the Right Database for Your Needs
The choice between SQL and NoSQL databases depends on your application's specific needs.
⚡ One HLD concept. 60 seconds. Interview ready
HLD: Shared DB vs Database per Service Trade-Offs
Choosing between a shared database and a database per service affects system design significantly.
⚡ 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.
⚡ 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
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
Protobuf and Schema Evolution: Avoid Breaking Changes
Protobuf schema evolution requires careful changes to avoid breaking existing clients.
⚡ One HLD concept. 60 seconds. Interview ready
HLD Timeout Pattern: Understanding Timeouts in Distributed Systems
A timeout indicates a deadline was exceeded, not necessarily a failure.
🧠Related by meaning
Not tagged “system design”, but closely connected
