How deeply does ASP.NET Core in Action, 3e cover strangler pattern?

Explains the incremental strategy and names supporting tools, but stops short of detailed routing or deployment instructions.

Strangler pattern

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

The strangler fig pattern is an incremental modernization pattern in which new functionality gradually replaces parts of an existing system until the legacy system can be retired.

The strangler pattern modernizes an existing application through small iterations. New ASP.NET Core functionality gradually replaces selected pages or APIs while the existing application continues operating, reducing the risk of a full conversion. section 2.4.3

A practical migration can use:

System.Web adapters to support migration between application generations. section 2.4.3
YARP, a .NET reverse proxy, to help direct requests during the transition. section 2.4.3
Visual Studio tooling to move one page or API at a time instead of converting everything at once. section 2.4.3

Incremental ASP.NET migration

Move one page or API from an existing ASP.NET application to ASP.NET Core, verify the result, and continue with the next slice until the remaining legacy application can be retired. section 2.4.3

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

Google Anthos in ActionThe strangler fig pattern incrementally replaces parts of a legacy system with new implementations until the legacy system is reduced or removed.
liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureThe strangler fig pattern is a migration pattern that gradually replaces an existing system by routing increasing responsibility to a new system until the old system is no longer needed.
liveBook manning.com

Kafka for ArchitectsThe strangler fig pattern is an incremental replacement approach in which a new implementation gradually takes over functionality from a legacy system.

Compare how 4 books explain strangler pattern →

Related concepts

legacy systemaddresses · A legacy system is an existing software or computing system that remains in use or must be maintained despite older technologies, designs, or constraints that can complicate change.
feature flaguses · A feature flag is a configuration control that conditionally enables, disables, or selects a software feature or behavior.
microservice architectureused by · Microservice architecture is a software architectural style that organizes an application as independently deployable services with focused responsibilities that communicate through defined interfaces.
YAGNI principleimplements · The YAGNI principle is a software design discipline of avoiding functionality or structure until a concrete need for it arises.

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.