ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When serving large datasets using call.respondStream or ByteReadChannel , the goal is to maintain a low memory footprint by avoiding loading the entire collection into memory. While Ktor provides primitives to stream data in chunks, the interaction between the data source and the client-side consumption rate remains complex. Specifically, if a HTTP client co
Operators want Filebeat to ship log events reliably while avoiding alert fatigue caused by frequent notifications about internal queue backpressure. The goal is to distinguish transient queue fluctuations that are harmless from sustained conditions that could lead to data loss or processing delays. Filebeat’s memory queue offers low latency but can lose even
The goal is to select a backpressure exposure strategy for an Akka Streams pipeline that emits high‑frequency events to a WebSocket sink serving a UI client, while keeping the UI responsive and avoiding client‑side overload. Constraints include the need for the client to honor the chosen flow‑control mechanism, the trade‑off between latency introduced by bac
Context The OpenTelemetry Collector's OTLP exporters use a bounded sending_queue that fills when downstream backends exhibit latency or connection pool exhaustion. The documented default behavior is to drop telemetry data rather than apply backpressure to upstream receivers. Problem During intermittent connection pool exhaustion on the backend, the Collector
beats
akka
opentelemetry
ktor