I'm preparing for
Topic
system design
153 shorts across 1 course, in learning order
🎛️ Narrow downsubject · level · topic1▾
Results · 10 for “Kubernetes Services”
← Front page✨ Smart search: matched by meaning, not just words

⚡ One HLD concept. 60 seconds. Interview ready
Kubernetes Ingress: One Entry Point for Multiple Apps
Kubernetes Ingress allows one entry point for multiple applications, simplifying routing.

⚡ 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
Choosing Service Boundaries in Microservices Architecture
Choosing the right boundaries for microservices is crucial for effective architecture.

⚡ 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
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
Cascading Failures in Distributed Systems Explained
Cascading failures occur when one service's failure impacts others, causing widespread issues.

⚡ 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 the RED Method for Microservices Monitoring
The RED Method helps monitor microservices using Rate, Errors, and Duration metrics.

⚡ One HLD concept. 60 seconds. Interview ready
Distributed Backpressure: Managing Service Overload
Distributed backpressure helps manage the flow of work between services to prevent overload.

⚡ 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.
🧠Related by meaning
Not tagged “system design”, but closely connected

