> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-7-14-network-transmission-for-events.md).
# Day 7/14 Network Transmission for events
Day 7 of 14: Analyze event payloads from a TCP/IP perspective, exploring why single-packet events eliminate multiple ACK overheads to boost network efficiency.
System performance, in the context of data transmission and processing efficiency, is critical for optimizing operations. The size of redundant data blocks remains fixed, impacting bandwidth consumption and processing speed. Larger messages comprising multiple data blocks demand more resources, leading to slower processing and hindering overall workflow efficiency, particularly from a network perspective.\
\
\
Most of the event broker libraries (layer 7 application layer) are built on top of TCP/IP protocol (layer 4 transport layer). When events are transmitted from the Publisher to the consumer via the event broker, TCP breaks down the event into smaller packets, forwarding them to the Internet Protocol (IP) layer for transmission. These packets traverse various network components like firewalls, switches, and routers enroute to the destination, with the recipient required to acknowledge each packet within the same message before the source can proceed with the next message. TCP facilitates error recovery by re-transmitting missing packets until successful delivery or connection termination.\
\
The standard **TCP packet** size is 1,500 bytes, with the initial 20 bytes reserved for essential TCP header information such as source/destination ports, sequence numbers, and offsets. Single-package events prove more efficient than multi-package events, as they eliminate the need for managing multiple acknowledgments and re-transmission processes, enhancing operational effectiveness.\
\
Furthermore, the increasing support for **link aggregation (LAG)** in event broker enables the consolidation of multiple physical data links into a unified virtual link layer for network transmission. This approach streamlines the enhancement of network bandwidth by leveraging existing cable connections, promoting more effective bandwidth utilization. As illustrated in the provided diagram, smaller events offer superior efficiency by transmitting the same file through a single physical link, optimizing network resource allocation.\
## 🚀 Let's Connect Beyond GitBook!
If you found this article helpful, you can find more of my technical insights, daily discussions, and deep dives across these platforms:
* **Read more of my work:** Check out my articles on [dev.to](https://dev.to/stephen_tsoi_5b2c4055f3a9) and [Hashnode](https://stephentsoi.hashnode.dev/).
* **Join the daily conversation:** Connect with me directly on [LinkedIn](https://www.linkedin.com/in/stephen-tsoi-16309730/).
***
#### 📬 Stay Ahead of the Curve
Enjoyed this piece? I break down complex technical topics into bite-sized, actionable insights every week.
👉 **Subscribe to my** [**LinkedIn Newsletter**](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7487299517642612736) to never miss an update and get the latest articles delivered straight to your feed!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-7-14-network-transmission-for-events.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
