I'm preparing for
Topic
software architecture
11 shorts across 1 course, in learning order
🎛️ Narrow downsubject · level · topic1▾
Results · 9 for “Design patterns in software”
← 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
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
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
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: Microservices vs Modular Monolith Explained
Microservices and modular monoliths differ mainly in deployment and communication methods.
⚡ 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
HLD Timeout Pattern: Understanding Timeouts in Distributed Systems
A timeout indicates a deadline was exceeded, not necessarily a failure.
🧠Related by meaning
Not tagged “software architecture”, but closely connected
