liveBook · Manning

Infrastructure

Infrastructure is the foundational physical, digital, and operational resources and systems that support the operation of organizations, computing systems, or services.

How 11 Manning books explain it

Simple Object-Oriented Design: Create clean, maintainable applications

Infrastructure is the set of external systems, integrations, and technical resources outside the backend's direct control.

How it is used
Separates external communication from business logic to control coupling and change impact.
How deep it goes
Defines infrastructure, gives separation rules and repository examples, then examines abstraction and technology-specific tradeoffs without implementing caching.
Examples
Uses database access, configuration-file reading, remote employee calls, caching, read replicas, authentication changes, and S3 file storage.
What you can do after
Evaluate and refactor boundaries that isolate external dependencies while retaining useful infrastructure capabilities.

Read how Simple Object-Oriented Design: Create clean, maintainable applications explains infrastructure →

Secure APIs

Computing infrastructure is the collection of networks, servers, traffic-management components, and security controls that supports software operation.

How it is used
Supports API operation by combining networks, servers, traffic-management components, and security controls.
How deep it goes
Explains topology, controls, attack surfaces, and Infrastructure as Code, while deferring detailed infrastructure techniques to later treatment.
Examples
Uses a vulnerable avatar-download endpoint, user and admin services, network isolation, gateways, WAFs, and Infrastructure as Code tools.
What you can do after
Operate/configure API infrastructure by restricting service access, protecting traffic, replicating environments, and auditing infrastructure code.

Read how Secure APIs explains infrastructure →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

The computing resources and supporting systems that provide the foundation for running applications and services.

How it is used
Frames the resources and supporting systems needed to deliver applications reliably and securely in production.
How deep it goes
Defines infrastructure broadly, distinguishes core resources from operational requirements, and illustrates modern service examples.
Examples
Uses servers, switches, disks, databases, queues, containers, serverless functions, monitoring, alerts, and health checks.
What you can do after
Evaluate whether an application environment meets production requirements beyond basic compute, networking, and storage.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains infrastructure →

Shipping Go: Develop, deliver, discuss, design, and go again

The computing resources, platforms, networks, and supporting software systems required to develop, run, and deliver applications.

How it is used
Guides teams from shipping a visible product toward infrastructure changes driven by cost, scale, and delivery feedback.
How deep it goes
Frames infrastructure as a prioritization decision but stops short of implementation procedures or detailed platform design.
Examples
Uses a high cloud bill, AWS or Google deployment, load testing, special-character input, and Kubernetes as concrete cases.
What you can do after
Evaluate when infrastructure optimization or a more complex platform is justified by cost, scale, and team capacity.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains infrastructure →

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

Infrastructure is the computing, networking, storage, and operational foundation on which software runs.

How it is used
Guides modernization choices by treating infrastructure as a distinct technology dimension for each subsystem or subdomain.
How deep it goes
Compares infrastructure shifts through concrete alternatives and scoring, without detailing implementation mechanics.
Examples
Uses on-premises-to-cloud, virtual-machines-to-serverless, and Amazon Web Services as concrete infrastructure examples.
What you can do after
Evaluate modernization options by scoring how different the target infrastructure will be from the current environment.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains infrastructure →

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu

Infrastructure is the collection of computing, networking, storage, and related resources that support systems and services.

How it is used
Supports designing, creating, managing, and delivering infrastructure through Terraform.
How deep it goes
Explains providers, resources, state, backends, and workspaces, then stops short of detailed vendor-specific configuration.
Examples
Uses an AWS virtual machine, DNS records, repositories, and other provider-backed resources as concrete infrastructure examples.
What you can do after
Build it from scratch by mapping a system design to Terraform resources and providers.

Read how Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu explains infrastructure →

LLMs in Production

Infrastructure is the hardware, software, networking, and operational resources that support computing systems.

How it is used
Supports the machine learning life cycle by providing the operational foundation for LLM data, models, search, and production systems.
How deep it goes
Contrasts laptop-scale infrastructure with LLM production needs and demonstrates a local vector database setup, but stops short of full platform implementation.
Examples
Uses a laptop-based scikit-learn system, an LLM platform diagram, and a Docker-hosted Milvus instance as concrete infrastructure examples.
What you can do after
Operate/configure a local Milvus vector database and evaluate when laptop, in-memory, managed-cloud, or GPU-enabled infrastructure fits.

Read how LLMs in Production explains infrastructure →

Think Like a CTO

Infrastructure is the collection of computing, networking, storage, and operational components that support software execution.

How it is used
Separates back-office technology responsibilities from the product platform when clarifying organizational ownership.
How deep it goes
Distinguishes infrastructure from product technology and names examples, but stops short of implementation or operational procedures.
Examples
Uses desktop computers, mail servers, phones, printers, laptops, ISP contracts, and printer ink as infrastructure examples.
What you can do after
Evaluate whether infrastructure belongs with IT management, product technology leadership, or a blended small-company role.

Read how Think Like a CTO explains infrastructure →

AI Model Evaluation

Infrastructure is the computing, storage, networking, and runtime support required to operate a software system.

How it is used
Supports diagnostic offline evaluations, online A/B tests, and operational LLM-as-a-judge pipelines.
How deep it goes
Extends from tooling, data infrastructure, and logging to latency, capacity, costs, versioning, and reproducibility.
Examples
Uses logging, model serving, latency dashboards, GPU-cost guardrails, and versioned prompts as concrete infrastructure artifacts.
What you can do after
Operate/configure evaluation systems by measuring reliability, latency, capacity, cost, observability, and reproducibility alongside user metrics.

Read how AI Model Evaluation explains infrastructure →

Fundamentals of Cybersecurity

Infrastructure is the physical and digital foundation of an organization’s operations, including facilities, equipment, computing resources, networks, and managed information.

How it is used
Frames the physical and digital foundation organizations rely on and cybersecurity professionals work to protect.
How deep it goes
Defines infrastructure and compares deployment models, while deferring detailed cloud responsibility practices.
Examples
Uses buildings, servers, network equipment, websites, databases, email, and business applications as examples.
What you can do after
Evaluate where computing systems operate and who maintains them, ensures availability, and implements security controls.

Read how Fundamentals of Cybersecurity explains infrastructure →

Machines that Think

Infrastructure is the physical and networked foundation that supplies the computing, communication, and energy resources required to operate computational systems.

How it is used
Frames the material and organizational conditions that make large language model training and deployment feasible.
How deep it goes
Connects compute, hardware, networking, energy, and software-hardware fit to scale limits, without detailing engineering procedures.
Examples
Uses GPU and TPU access, cloud partnerships, and hardware-specific software stacks as examples of infrastructure choices.
What you can do after
Evaluate how access to compute, energy, and integrated platforms shapes which models can be trained and deployed at scale.

Read how Machines that Think explains infrastructure →

Also covered in

What to know first

Related concepts

Questions about infrastructure

What is infrastructure?

Infrastructure is the foundational physical, digital, and operational resources and systems that support the operation of organizations, computing systems, or services.

Which Manning books explain infrastructure?

Simple Object-Oriented Design: Create clean, maintainable applications, Secure APIs, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform, Shipping Go: Develop, deliver, discuss, design, and go again, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu, LLMs in Production, Think Like a CTO and 3 more.

What should I know before learning infrastructure?

Manning books that teach infrastructure usually introduce contract, deployment pipeline, software testing and authentication first.

What is the difference between infrastructure and business logic?

Infrastructure is the foundational physical, digital, and operational resources and systems that support the operation of organizations, computing systems, or services. Business logic is the domain-specific rules, computations, and decisions that determine how a software system processes operations and behaves.

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.