How deeply does ASP.NET Core in Action, 3e cover single responsibility principle?

Explains the definition, applies it to e-commerce services, and connects it to dependency construction without detailing implementation registration.

Single responsibility principle

As explained in ASP.NET Core in Action, 3e

The single-responsibility principle is a design principle stating that a class should have responsibility for one piece of functionality and change only when that functionality changes.

The single-responsibility principle (SRP) keeps each class responsible for one piece of functionality and limits its reasons to change. Small, independent services can then combine into a complete application. section 3.7.1

An order total built from focused services

An e-commerce application can use TaxCalculator for tax, ShippingCostService for shipping, and OrderTotalCalculator to combine both results. OrderTotalCalculator should use those services rather than calculate every concern itself. section 3.7.1

SRP encourages a practical separation of responsibilities:

Give each class one independent piece of functionality. section 3.7.1
Avoid combining service use with dependency construction; dependency injection lets another class provide required services. section 3.7.1

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Software Design for Python ProgrammersThe Single Responsibility Principle states that a class should have one primary responsibility and remain cohesive around it.
liveBook manning.com

The Art of CodeThe Single Responsibility Principle is an object-oriented design principle stating that a class should have only one reason to change.
liveBook manning.com

Object-Oriented Software Design in C++A design principle stating that a class should have one major responsibility.
liveBook manning.com

.NET MAUI in ActionThe single-responsibility principle is a software design principle stating that a component should have one primary reason to change.
liveBook manning.com

Unit Testing Principles, Practices, and PatternsThe Single Responsibility Principle states that a class or module should have one responsibility and one reason to change.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsThe single responsibility principle is a software design principle stating that a component should have one primary responsibility and one reason to change.

Compare how 7 books explain single responsibility principle →

Related concepts

principlekind of · A principle is a general rule, guideline, or value that guides decisions, behavior, or judgments.
cohesive classimplemented by · A class whose methods and instance variables collectively serve one closely related primary responsibility.
SOLID principleskind of · The SOLID principles are five object-oriented software-design principles concerning single responsibility, openness to extension, substitutability, interface segregation, and dependency inversion.
separation of concernsimplements · Separation of concerns is a design principle that organizes a system so distinct responsibilities are handled by separate, independently manageable parts.
functionconfigures · A function is a callable program unit that performs an operation, may accept inputs, and can produce a result or side effect.
pipeline componentimplemented by · A pipeline component is a discrete, executable stage in a data or machine-learning workflow that performs an operation and may consume or produce data artifacts.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.