Understanding lag in a streaming pipeline
Blog post from New Relic
New Relic's observability platform handles pipeline latency by attempting to keep data in order, buffering and reordering data, dynamically adapting to latency with strategies like traffic flow, time waves, and external observers. The goal is to design a system where latency has less impact, while also addressing challenges such as blockages in the pipeline and lack of information for uninstrumented paths. By combining these strategies and scoping them appropriately, New Relic aims to dynamically adjust buffering and processing to improve pipeline performance and resilience.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Observability | 6 | 1,101 | 190 | 79 | -6% |
| Real-time | 5 | 2,223 | 570 | 156 | -11% |
| Data Pipeline | 1 | 462 | 121 | 62 | +58% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.