Single Responsibility
A class should have only one reason to change, meaning it should have only one job or responsibility. Promotes high cohesion and reduces coupling between components.
Single Responsibility: One Reason to Change
Why a class with many jobs has many reasons to change — and why that is a bug.
Single Responsibility in Production: Services and Modules
Responsibility boundaries in services, modules, and teams.
Advanced Single Responsibility: Transactions and Bounded Contexts
When responsibilities must cooperate, and domain boundaries that stay honest under transactions.
Single Responsibility: Review & Mastery Quiz
Scenario questions on reasons to change, services, and boundaries.
Free Books & Guides
Official Documentation
Video Courses
Single Responsibility — Explained (YouTube)
A video explanation of the Single Responsibility principle with practical examples.
freeCodeCamp — Software Architecture Course
A comprehensive course covering software architecture principles, patterns, and best practices.
ByteByteGo — Distributed Systems
High-quality animated explanations of system design principles, distributed systems, and architecture patterns.