liveBook · Manning

Pull model

A pull model is a pattern in which a consumer or recipient initiates requests for data, messages, configuration, or work according to its needs or readiness.

How 4 Manning books explain it

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A pull model is an automation pattern in which managed systems periodically connect to a management system and retrieve configuration.

How it is used
Contrasts client-initiated configuration retrieval with server-initiated automation in infrastructure as code.
How deep it goes
Defines request direction, agent architecture, workload distribution, and update delays, but does not detail agent implementation.
Examples
Uses Puppet and Chef agents retrieving configurations from central servers, contrasted with Ansible and Terraform push workflows.
What you can do after
Evaluate whether distributed check-ins or centralized immediate updates better suit an organization and network.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains pull model →

The Joy of JavaScript

A communication or data-flow model in which a consumer requests data when it needs it.

How it is used
Frames consumer-initiated data access and contrasts it with producer-controlled push communication.
How deep it goes
Defines producer-consumer control and demonstrates functions, iterator next calls, arrays, and polling, without implementing a standalone pull abstraction.
Examples
Uses function calls, iterator next calls, array indexing, Symbol.iterator, and interval-based long polling as concrete pull examples.
What you can do after
Apply it via JavaScript functions, iterators, and array access when consumers should control when data is requested.

Read how The Joy of JavaScript explains pull model →

Spring in Action, Sixth Edition

A pull model is a messaging consumption pattern in which a consumer explicitly requests or retrieves messages, potentially waiting until one is available.

How it is used
Controls when a consumer requests and processes messages from a broker.
How deep it goes
Explains blocking retrieval, destination choices, and conversion, but stops short of broader listener implementation details.
Examples
Uses TacoOrder messages pulled from the tacocloud.order.queue destination with receive or receiveAndConvert.
What you can do after
Operate/configure a JMS consumer that retrieves raw messages or converted domain objects through JmsTemplate.

Read how Spring in Action, Sixth Edition explains pull model →

Learn Docker in a Month of Lunches, Second Edition

A pull model is a data-collection approach in which a monitoring system periodically fetches data from monitored systems.

How it is used
Uses periodic scraping to collect application metrics from containerized services.
How deep it goes
Explains scraping configuration, target discovery, intervals, and scaling caveats without detailing Prometheus internals.
Examples
Uses a Prometheus YAML configuration, scaled access-log containers, generated HTTP requests, and a PromQL aggregation.
What you can do after
Operate/configure Prometheus jobs that scrape fixed or DNS-discovered containers and verify collected metrics.

Read how Learn Docker in a Month of Lunches, Second Edition explains pull model →

Related concepts

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.