A computer network interconnects computers and devices to enable communication and resource sharing. It comprises physical links, protocols (e.g. TCP/IP), switching and security mechanisms, and topology choices. Networks underpin distributed systems and directly affect latency, availability, and scalability. They guide design decisions across architecture, s…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A computer network connects computers and devices so they can exchange data, provide services, and share resources. It includes links, protocols, addressing, forwarding, and security mechanisms.
Computer networks emerged from the practical problem of connecting computers and devices reliably across separate locations while allowing shared use. The Internet Protocol already described packet-switched, interconnected networks in 1981, showing that addressing, routing, and fragmentation are the core functions of this kind of connectivity.
Think of a network as a layered traffic system. At the bottom, cables or radio carry bits between nodes. Above that, protocols define how data is split into packets, addressed, and transmitted. Switches and routers choose the next hop; topology and capacity shape paths, speed, and resilience. Security mechanisms limit who can reach which parts.
Devices and their wired or wireless connections form the network's basic structure.
Packets need clear destination information so they can reach the right recipient.
Shared rules define formats, procedures, and error handling for communication.
Network components choose the next path and connect smaller networks into a larger whole.
The arrangement of nodes and links affects paths, redundancy, and failure behavior.
Segmentation, access control, and firewalls limit visibility and attack surface.
Computer networks matter when systems must work across sites, cloud, and datacenter boundaries, when latency, bandwidth, availability, or segmentation shape architecture decisions, or when outages and misconfigurations need investigation. More control and isolation usually come with more complexity, operating cost, and troubleshooting effort.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.