How deeply does Building Web APIs with ASP.NET Core cover separation of concerns?

Defines the principle and its benefits, then applies it conceptually to REST without developing a detailed implementation.

Separation of concerns

As explained in Building Web APIs with ASP.NET Core

Separation of concerns is a design principle that partitions a system so distinct responsibilities are handled independently.

Separates distinct responsibilities so each part of a system can be handled independently. In REST, this means keeping the user interface and data storage concerns apart. section 1.1.4

Applying the principle supports several practical system qualities:

Improves portability by allowing clients and server-side data concerns to evolve separately. section 1.1.4
Keeps implementations simpler to build and maintain. section 1.1.4
Contributes to system scalability and modifiability. section 1.1.4

Browser and web application

A browser acts as a client with a separate role from the web application and does not need to know how that application was implemented. This boundary illustrates separation between interface and data-related responsibilities. section 1.1.4

How Building Web APIs with ASP.NET Core covers it

Cover of Building Web APIs with ASP.NET Core

liveBook manning.com

Read Building Web APIs with ASP.NET Core on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Practices of the Python ProA software design technique that organizes a system so each part addresses a distinct concern and dissimilar concerns remain isolated.
liveBook manning.com

A Pythonic Adventure: From Python basics to a working web appSeparation of concerns is a software design principle that divides a system into components with distinct responsibilities.
liveBook manning.com

C++ Concurrency in Action, Second EditionSeparation of concerns is a software design principle that organizes a system so distinct concerns are handled independently.
liveBook manning.com

Machine Learning Platform EngineeringSeparation of concerns is a software design principle that isolates distinct responsibilities into separate components or layers.
liveBook manning.com

Coding with AISeparation of concerns is a design principle that assigns distinct responsibilities to separate software components so they do not overlap unnecessarily.
liveBook manning.com

Build Python Web Apps with StreamlitSeparation of concerns is a software design principle in which distinct components focus on distinct responsibilities and interact through controlled interfaces.
liveBook manning.com

ASP.NET Core in Action, 3eSeparation of concerns is a design principle that isolates distinct aspects of an application so each can change with minimal impact on the others.
liveBook manning.com

Akka in Action, Second EditionSeparation of concerns is the division of software into parts whose responsibilities are distinct and independently manageable.
liveBook manning.com

The Art of CodeSeparation of concerns is a design technique that divides software into parts responsible for distinct concerns so that each can change more independently.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellSeparation of concerns is a design principle that isolates distinct responsibilities so they can be understood and changed independently.
liveBook manning.com

Build AI-Enhanced Web AppsSeparation of concerns is a software design principle that divides a system into parts with distinct responsibilities.
liveBook manning.com

Build and Orchestrator in Go (From Scratch)Separation of concerns is a software design principle that assigns distinct responsibilities to separate components or modules.
liveBook manning.com

AI Agents in Action, Second EditionSeparation of concerns is a software design technique that isolates distinct responsibilities so they can be developed and changed independently.
liveBook manning.com

The Creative ProgrammerSeparation of concerns is the organization of a system so that distinct responsibilities or decision criteria remain independently managed.
liveBook manning.com

Authorization in ActionSeparation of concerns is a design principle that divides a system into parts with distinct responsibilities and limited overlap.
liveBook manning.com

React Quickly, Second EditionSeparation of concerns is a design principle that isolates distinct responsibilities so each part of a system handles a focused concern.
liveBook manning.com

Elixir in Action, Third EditionSeparation of concerns is a design technique that divides a system into components with distinct responsibilities.
liveBook manning.com

Learn Go with Pocket-Sized ProjectsSeparation of concerns is a design principle that assigns distinct responsibilities to separate software components.
liveBook manning.com

Tiny CSS ProjectsSeparation of concerns is a software design principle that divides a system into distinct sections with separate purposes.
liveBook manning.com

Rust Servers, Services, and AppsSeparation of responsibilities is a design principle that assigns distinct concerns to different software components.
liveBook manning.com

Python Concurrency with asyncioSeparation of concerns is a design technique that gives distinct responsibilities to separate components or computations.

Compare how 22 books explain separation of concerns →

Related concepts

concernuses · A concern is a distinct responsibility, requirement, or aspect of behavior that a software system must address.
single responsibility principleimplements · The single responsibility principle is a software design principle that gives a component one focused responsibility and one primary reason to change.

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.