From bd6c8982dbc3e2e98ef4d6d0315d12fda89931ab Mon Sep 17 00:00:00 2001 From: Tigran Najaryan Date: Tue, 17 Dec 2024 16:32:18 -0500 Subject: [PATCH] Explicitly state that Otel/STEF limitations must be explored --- projects/stef.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/projects/stef.md b/projects/stef.md index 3e6114845..9367c41d4 100644 --- a/projects/stef.md +++ b/projects/stef.md @@ -38,7 +38,7 @@ The design principles are: Design non-goals are: - Random access to data by seeking to an arbitrary point in the stream. -- Ability to keep the entire data batch in memory efficient and traverse it for +- Ability to keep the entire data batch in memory efficiently and traverse it for processing purposes. Otel/STEF is not a replacement for Protobuf-based OTLP. - Ability to query (search) data by some criteria. Otel/STEF does not target Parquet's niche. @@ -54,6 +54,9 @@ The project goals are the following: - Add Otel/STEF exporter and Otel/STEF receiver to Otel Collector. - Publish benchmark-justified guidelines on applicability of Otel/STEF vs OTLP vs Otel Arrow. +- Explore the limitations of Otel/STEF, the impact of its statefulness and + persistent connection on load balancers and servers that accept a large number of + connections. - Refine and stabilize Otel/STEF specification and encourage its implementation inside or outside Otel. - Evaluate additional use-cases that can be served by Otel/STEF, for example