Sexy new codebase antipattern

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

The sexy new codebase antipattern is a migration approach that stops feature development in a legacy system and builds new features separately while retaining substantial coupling to the legacy system.

The sexy new codebase antipattern freezes feature development in a legacy monolith and moves new work into a cleaner, more exciting codebase. The apparent improvement fades when the new system still depends heavily on the legacy system for integration and synchronization. section 12.4.2

Look for these warning signs:

• Teams seek faster change by separating development, but significant new functionality still depends on legacy behavior. section 12.4.2
• The new codebase becomes tightly coupled and difficult to change because domain boundaries were never clearly defined. section 12.4.2
• Avoidance requires defining architectural boundaries around carefully understood domain boundaries rather than adding another layer over legacy code. section 12.4.2

Figure 12.21 The bubble migration pattern

Use the bubble migration pattern as a nearby migration pattern when comparing isolated new development with continued legacy coupling. section 12.4.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Explains the motivation, coupling failure, domain-boundary cause, and avoidance principle without prescribing implementation steps.

Examples

Uses the recurring case of a new codebase whose features require integration and synchronization with the legacy system.

What it assumes

Assumes familiarity with legacy systems and architectural coupling while teaching domain boundaries as the key avoidance principle.

What you can do after

Diagnose whether a modernization effort has separated development without separating meaningful domain responsibilities.

How it connects

Connects legacy monoliths, domain boundaries, architectural boundaries, bubble migration, and migration patterns.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.