English
Microservices Architecture - Structured Study Notes
These notes keep the lecture flow: boundaries, communication, state, and resilience.
SECTION 1: Failures Exceptions Normal
Topic: Failures Exceptions Normal
Core idea: Failures are not exceptions — they are normal.
Explanation: Distributed failures are normal, so services need guardrails: strict timeouts, bounded retries with backoff, circuit breakers, and idempotency.
Practical example: In a real system, this appears during release pressure: failures are not exceptions — they are normal.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
Topic: Failures Exceptions
Core idea: Failures are not rare exceptions.
Explanation: Distributed failures are normal, so services need guardrails: strict timeouts, bounded retries with backoff, circuit breakers, and idempotency.
Practical example: In a real system, this appears during release pressure: failures are not rare exceptions.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
SECTION 2: Every Single Failure
Topic: Every Single Failure
Core idea: It does not try to stop every single failure.
Explanation: Distributed failures are normal, so services need guardrails: strict timeouts, bounded retries with backoff, circuit breakers, and idempotency.
Practical example: In a real system, this appears during release pressure: it does not try to stop every single failure.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
Topic: Continue Working Problems
Core idea: They can also continue working even when problems happen.
Explanation: Distributed failures are normal, so services need guardrails: strict timeouts, bounded retries with backoff, circuit breakers, and idempotency.
Practical example: In a real system, this appears during release pressure: they can also continue working even when problems happen.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
SECTION 3: Ensures Systems Remain
Topic: Ensures Systems Remain
Core idea: This ensures systems remain reliable.
Explanation: This ensures systems remain reliable.
Practical example: In a real system, this appears during release pressure: this ensures systems remain reliable.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
Topic: Could Website Loading
Core idea: This could be a website not loading.
Explanation: This could be a website not loading.
Practical example: In a real system, this appears during release pressure: this could be a website not loading.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
SECTION 4: When Incident Happens
Topic: When Incident Happens
Core idea: When an incident happens, human action is needed.
Explanation: When an incident happens, human action is needed.
Practical example: In a real system, this appears during release pressure: when an incident happens, human action is needed.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.
Topic: Problems Services Incidents
Core idea: Problems like services being down are incidents.
Explanation: Problems like services being down are incidents.
Practical example: In a real system, this appears during release pressure: problems like services being down are incidents.
Common mistake: A common mistake is confusing this topic with a similar term.
Connection: This topic connects to other lecture ideas by sharing cause and effect steps.