In-Memory Queue vs Persistent Queue: Which Is Best for Low‑Traffic Beats?
Goal Determine the most cost‑effective queue strategy for Elastic Beats when the monitored traffic is minimal. Constraints Beats provide two documented queue implementations: In‑memory queue – low CPU and disk I/O, but loses buffered events on crash. Persistent disk queue – writes events to local storage before shipping, adding durability at the expense of h
beats