liveBook · Manning

Architectural style

Also called architectural pattern, architecture pattern

An architectural pattern is a reusable high-level organization of software components, interactions, and constraints for addressing recurring system-design concerns.

How 3 Manning books explain it

Retrieval Augmented Generation, The Foundational Ideas

An architectural pattern is a recurring high-level organization of software components and their interactions.

How it is used
Organizes retrieval-augmented generation around connecting generative models to relevant external knowledge.
How deep it goes
Defines component roles and contrasts flat retrieval with hierarchical retrieval, but does not specify a complete architecture implementation.
Examples
Contrasts a date lookup with a historical synthesis question, then uses RAPTOR’s tree organization to address flat retrieval.
What you can do after
Evaluate/understand it by linking retrieval failures to architectural choices and adding complexity only when a measured baseline warrants it.

Read how Retrieval Augmented Generation, The Foundational Ideas explains architectural style →

Microservices Patterns, Second Edition

An architectural style is a set of structural principles that defines the permissible components, connectors, and composition constraints for a family of software systems.

How it is used
Defines structural rules for shaping an application’s architecture and organizing its components and connectors.
How deep it goes
Specifies component and connector vocabularies and composition constraints, and notes that applications often combine styles.
Examples
Uses building styles as an analogy and names layered, hexagonal, monolithic, and microservice architectures.
What you can do after
Understand how a style constrains an architecture and use its elements and relations to define an architectural view.

Read how Microservices Patterns, Second Edition explains architectural style →

Architecting for Autonomy

A recurring architectural blueprint describing a solution structure, component interactions, and architectural constraints.

How it is used
Structures agentic-system design by defining interactions, runtime policy enforcement, and integration with existing platforms.
How deep it goes
Defines recurring blueprints and failure boundaries but leaves implementation verification to playbooks and day-to-day control to practice.
Examples
Uses the Policy Gateway, pre-execution policy evaluation, fail-closed behavior, and routing to human review.
What you can do after
Evaluate/understand how autonomous actions receive explicit authority, constraints, supervision, and failure handling.

Read how Architecting for Autonomy explains architectural style →

Also covered in

What to know first

Related concepts

Questions about architectural style

What is architectural style?

An architectural pattern is a reusable high-level organization of software components, interactions, and constraints for addressing recurring system-design concerns.

Which Manning books explain architectural style?

Retrieval Augmented Generation, The Foundational Ideas, Microservices Patterns, Second Edition and Architecting for Autonomy.

What should I know before learning architectural style?

Manning books that teach architectural style usually introduce language model, Python and contract first.

What kinds of architectural style are there?

Kinds of architectural style include microservice architecture, retrieval-augmented generation, hexagonal architecture, agent mesh, BEM and CQRS.

What is architectural style also called?

Architectural style is also called architectural pattern or architecture pattern.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.