liveBook · Manning

Network topology

Network topology is the structural arrangement and connectivity relationships among the components of a network or system.

How 3 Manning books explain it

Deep Learning with R, Third Edition

Network topology is the structural arrangement and connectivity pattern of a neural network's layers and operations.

How it is used
Defines how layers connect and constrains the functions a model can learn for a task.
How deep it goes
Explains topology through stacks, branches, feature hierarchies, and architecture assumptions; defers detailed construction of nonsequential models.
Examples
Uses an R/Keras Dense classifier, a Transformer layer graph, and repeated Xception convnet blocks.
What you can do after
Evaluate/understand whether an architecture’s connections and assumptions suit the data, then tune layers using validation results.

Read how Deep Learning with R, Third Edition explains network topology →

Secure APIs

Network topology is the arrangement and connectivity relationships among networks, hosts, and communication components.

How it is used
Shapes API security threat models by controlling exposure, permitted traffic, and movement between infrastructure components.
How deep it goes
Defines segmentation, public and private subnets, bridges, and DMZs, but stops short of comprehensive network-security coverage.
Examples
Uses segmented public and private networks, DMZ gateways, bastion servers, and separated public, internal, and development endpoints.
What you can do after
Evaluate API infrastructure, restrict sensitive resources, isolate services, and channel external traffic through controlled front-facing components.

Read how Secure APIs explains network topology →

Kafka for Architects

A graph topology is a directed processing structure that defines how streaming records traverse processing steps.

How it is used
Defines how streaming records flow through processing steps, from input Kafka topics to output topics.
How deep it goes
Explains graph nodes, edges, state stores, task assignments, and event traversal through the processing graph.
Examples
Illustrates source-to-sink event flow and custom processing for anomaly detection or fraudulent-transaction detection.
What you can do after
Build it from scratch by defining processors and their connections, or test a topology with TopologyTestDriver.

Read how Kafka for Architects explains network topology →

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.