Make Unary gRPC the only recommended mode

Experiments have shown that Streaming implementation results in significantly more complex code. The performance benefits of Streaming mode were only visible in very small batches and are not applicable to real life scenarios when under high load we aim to have large batches. In addition, one of the potential benefits that we could get with Streaming - the ability to optimize and avoid repetition of Resource does not seem to have much real life usage. As a result Streaming mode was removed from the RFC and Unary mode is the only mode that is now part of the spec.
open-telemetry · Sep 25, 2019 · 9fe913b · 9fe913b
1 parent 715a046
commit 9fe913b
Show file tree

Hide file tree

Showing 9 changed files with 425 additions and 515 deletions.
diff --git a/text/0000-opentelemetry-protocol.md b/text/0000-opentelemetry-protocol.md
diff --git a/text/0035-opentelemetry-protocol.md b/text/0035-opentelemetry-protocol.md
diff --git a/text/images/otlp-concurrent.png b/text/images/otlp-concurrent.png
diff --git a/text/images/otlp-load-balancing-timeline.png b/text/images/otlp-load-balancing-timeline.png
diff --git a/text/images/otlp-load-balancing.png b/text/images/otlp-load-balancing.png
diff --git a/text/images/otlp-multi-destination.png b/text/images/otlp-multi-destination.png
diff --git a/text/images/otlp-sequential.png b/text/images/otlp-sequential.png
diff --git a/text/images/otlp-streaming.png b/text/images/otlp-streaming.png
diff --git a/text/images/otlp-unary.png b/text/images/otlp-unary.png