technologybriefs
10:11in productionCh. 1 · Origins in resource sharing/ 10:11 · ceiling 15 min
Systems · Tech history

Internet

U.S. Department of Defense (DARPA) · 1969

The Internet was not built to connect people—it was built to survive fragmentation.

The Internet is a system for internetworking—designed to link disparate networks using standardised protocols. DARPA commissioned its core development in the 1970s. TCP/IP standardisation in 1982 enabled global proliferation. Its layered architecture and decentralised governance remain defining features—and enduring constraints.

SystemsTech historyComputingInfrastructureInternet cultureComputing across the network →
Chapters & takeaways4
  1. 1:05
    Origins in resource sharing

    The Internet began with time-sharing and packet switching—not email or websites.

  2. 2:46
    A military contract, not a military system

    DARPA commissioned the work—not invented it outright.

  3. 4:13
    The protocol proposal

    Cerf and Kahn’s 1974 paper defined the core logic of internetworking.

  4. 6:22
    Standardisation, not invention, scaled it

    TCP/IP standardisation in 1982—not ARPANET launch—enabled global proliferation.

Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • interoperability across heterogeneous networks
  • decentralised governance
  • layered architecture enabling independent evolution
What does not
  • guarantee security
  • enforce identity
  • ensure reliability
Study it if
  • network engineers
  • protocol designers
  • infrastructure architects
Skip it if
  • product managers expecting plug-and-play connectivity
  • policy makers assuming built-in accountability
The written brief1 min read

What it is and the problem it solves

The Internet is a system for internetworking—connecting dissimilar networks using shared protocols. It solves the problem of incompatible network architectures by standardising how data moves between them.

How it works

It uses packet switching to break data into discrete units routed independently across heterogeneous networks. It layers protocols—TCP for reliable delivery, IP for addressing and routing—to enable interoperability without central control.

What works

TCP/IP standardisation in 1982 enabled scalable, cross-border interconnection. Packet switching and time-sharing research provided the foundational mechanisms. Decentralised governance and layered architecture allow continuous evolution without top-down control.

What does not

It does not guarantee security, reliability, or fairness by design. It does not enforce trust, identity, or quality of service. Its success depends on voluntary adoption and coordination—not technical inevitability.

What it changes

It changes how networks relate: from isolated, proprietary systems to loosely coupled, protocol-governed internets. It shifts authority from hardware owners to protocol implementers and standards bodies.

Is it worth your time

Yes—if you work with networked systems, interoperability, or infrastructure design. Its layered architecture and decentralised governance remain operational constraints and enablers for all digital communication.

Same field · Systems4 of 184
9:36
Apache ActiveMQ2006ActiveMQ is a Java-based open source message broker implementing JMS 1.1. It enables asynchronous communication across Java and cross-language clients. It supports clustering, multiple persistence options, and several protocols. It originated in 2004 at LogicBlaze, moved to Apache in 2007, and later expanded to include Artemis—a next-generation broker donated in 2015. It is used in enterprise service buses and SOA infrastructure.
9:44
APIAPIs are interfaces—not features, not products, not platforms. They are contracts between machines. Their value lies in enforced abstraction: hiding complexity while exposing stability. That contract fails when documentation decays, versions collide, or legal uncertainty overrides engineering intent. They are indispensable—and fragile.
10:28
Unmanned surface vehicleUSVs are operational—but not systemic. They deliver real results in niche applications. They lack standardisation, interoperability, and regulatory grounding. Their value lies in removing humans from risk—not in replacing captains with code.
10:32
Self-driving truckSelf-driving trucks are a systems-level adaptation of autonomous technology to freight logistics. They rely on multi-sensor fusion and AI navigation, but their real-world deployment is bounded—not by capability, but by self-imposed safety thresholds and infrastructural control. Kodiak’s December 2024 launch on private lease roads is the first commercial driverless operation in the U.S., yet no autonomous truck has hauled freight without a human on public highways. What works is geofenced, industrial, or military convoy logic—not open-road autonomy.
Up next in Technology

Jacquard machine

Joseph Marie Jacquard · 1801 · 9:52

It did not compute — but it taught machines how to read instructions from outside themselves.

Play nextBack to Systems
9:52