Glossary · Data, timing and communication
Buffering
In systems engineering, buffering is the temporary storage of data or events before they are processed or transmitted. A buffer decouples producers and consumers that work at different rates or are briefly unavailable.
- Data and interfaces
- Integrated systems
In one sentence
Buffering holds data or events temporarily between systems; buffer size, overflow and age rules decide whether buffered data can still be trusted.
Example
An AGV stores position and battery events in a local buffer while it passes through a Wi-Fi dead zone and sends them to the fleet manager once it reconnects.
How it applies
- Integrated systems: Define the buffer size, what happens on overflow (drop the oldest entries, drop the newest, or block the producer) and the order in which buffered data is delivered.
- Functional safety: Buffered data arrives late. A consumer that acts on it must check its timestamp and treat data older than the allowed age as stale data. Buffers also add variable delay, which counts against the response time of any function that relies on the data.
- Evidence: Buffer overflows lose data silently unless they are logged. Make overflow counters part of the diagnostics, and of the audit trail where records must be complete.
Buffering vs. store-and-forward
Buffering is short-term, often in memory, and smooths differences in rate. Store-and-forward is a communication method that deliberately keeps data until the next system can receive it, often across longer outages.