Loading content
The User Datagram Protocol (UDP) is a connectionless transport protocol in the Internet protocol suite. It provides minimal headers, low latency and no connection management, making it suitable for streaming, DNS and real-time communication. UDP forgoes reliability and ordering, so applications must implement error handling and retransmission.
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.
UDP is a connectionless transport protocol that sends datagrams with little overhead and no delivery or ordering guarantee.
UDP was designed by David P. Reed and documented in RFC 768 in 1980. It emerged as a deliberately lightweight complement to TCP for applications that need their own reliability mechanisms or low latency.
The sender addresses each datagram and passes it to IP. UDP keeps no connection state, acknowledgements, or retries; the application decides how to handle loss, ordering, and pacing.
Datagrams are sent without establishing a session.
UDP avoids state management and acknowledgements.
The application defines behavior for lost packets.
UDP suits real-time, broadcast, and request protocols where low overhead matters more than automatic delivery guarantees.
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.