Big ball of mud architecture

Q: How deeply does Architecture Modernization: Socio-technical alignment of software, strategy, and structure cover big ball of mud architecture?

Illustrates the pattern through a scalability failure and stops short of prescribing implementation-level refactoring.

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

A software architecture whose structure has become tangled, difficult to understand, and resistant to change.

A big ball of mud architecture is a tangled, difficult-to-change structure that can block business growth when existing constraints no longer fit the product. section 3.2.1

Connected boats constrained by legacy architecture

A company pursuing internet-connected boat experiences built its platform on premises with an SQL database, home-rolled event-driven capabilities, and a big ball of mud architecture. The system handled only around five connected devices concurrently, although the business model required thousands. Architecture modernization became necessary to support the growth strategy. section 3.2.1

The example highlights several diagnostic signals:

Architecture constraints prevent the system from meeting the required scale. section 3.2.1
Technical modernization gains traction when leaders connect it to a concrete business outcome rather than unexplained jargon. section 3.2.1

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

Cover of Architecture Modernization: Socio-technical alignment of software, strategy, and structure

liveBook manning.com

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

Related concepts

monolithic architectureproduced by · Monolithic architecture is a software architecture in which an application's major functionality is organized and deployed as a single integrated unit.
workaroundproduced by · A workaround is an alternative procedure or implementation that bypasses or mitigates a problem or limitation without necessarily correcting its underlying cause.
model architecturecontrasts with · The structural organization of a computational system’s components, relationships, and operations that determines how it processes information or behaves.
system boundarycontrasts with · A system boundary is a defined separation that delimits the scope and responsibilities of a system or its parts and shapes how they interact with other parts or their environment.

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.