Architectural style
An architectural pattern is a reusable high-level organization of software components, interactions, and constraints for addressing recurring system-design concerns.
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
- Digital Twins in Action
- Writing for Developers: Blogs that get read
- Platform Engineering on Kubernetes
- Tiny CSS Projects
- Functional Design and Architecture: Examples in Haskell
- Fast by DefaultIn early access (MEAP)
- F# in Action: A Revised Edition of Get Programming with F#
- Grokking AI Algorithms, Second Edition
What to know first
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
- PythonPython is a high-level, general-purpose, dynamically typed programming language with readable syntax and support for multiple programming paradigms.
- contractA contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
Related concepts
- microservice architectureincludes · Microservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
- retrieval-augmented generationincludes · Retrieval-augmented generation is a technique that retrieves relevant information from external sources and supplies it as context to a generative model when producing an output.
- hexagonal architectureincludes · Hexagonal architecture is a software architecture pattern that isolates an application's core logic behind ports and connects external systems through adapters.
- agent meshincludes · A coordination architecture in which multiple agents interact through supervisory, brokered, and peer-to-peer structures under defined contracts, authority, paths, and evidence obligations.
- BEMincludes · BEM, or Block-Element-Modifier, is a CSS naming methodology that organizes classes around reusable blocks, their elements, and their modifiers.
- CQRSincludes · CQRS is an architectural pattern that separates operations and models for changing application state from those for reading or querying it.
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.


