Loading content
Transmission Control Protocol (TCP) is a core transport-layer protocol that provides reliable, ordered, and error-checked delivery of a byte stream between applications. It implements flow control, congestion control and retransmission to ensure data integrity over unreliable networks. TCP is fundamental for many internet services and influences system archi…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
TCP is a connection-oriented transport protocol that transfers data reliably, in order, as a byte stream between applications.
TCP emerged in the 1970s from Vint Cerf and Bob Kahn’s ARPANET research and was standardized in RFC 793 in 1981. The approach aimed to connect different networks through a common, robust transport method.
Endpoints establish a connection before exchanging data. Sequence numbers, acknowledgements, and retransmissions preserve order and completeness; flow and congestion control adapt the sending rate.
Endpoints establish state before exchanging data.
Acknowledgements and retries protect delivery.
Flow and congestion controls limit the sending rate.
TCP underpins applications that need complete, ordered data, including HTTP and database connections.
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.