From 377d3dbec3d1b5d0a3fd6246702fb45d22328ab3 Mon Sep 17 00:00:00 2001 From: Andreas Motl Date: Wed, 17 Dec 2025 02:43:30 +0100 Subject: [PATCH] Documentation: Add page about enumerating use cases --- docs/source/index.rst | 1 + docs/source/use-cases.rst | 28 ++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 docs/source/use-cases.rst diff --git a/docs/source/index.rst b/docs/source/index.rst index 8419064a..5095916b 100644 --- a/docs/source/index.rst +++ b/docs/source/index.rst @@ -123,3 +123,4 @@ data streaming systems like `Apache Flink `_, async.rst plotting.rst plugins.rst + use-cases.rst diff --git a/docs/source/use-cases.rst b/docs/source/use-cases.rst new file mode 100644 index 00000000..15fd0142 --- /dev/null +++ b/docs/source/use-cases.rst @@ -0,0 +1,28 @@ +Use cases +========= + +ETL applications +---------------- + + In LorryStream_, we use Streamz at the core for relaying data from streaming + sources into CrateDB_, because we have been looking for something smaller + and more concise than Beam, Flink, or Spark. Streamz gives us the freedom + to use advanced stream processing and flow control primitives within Python + applications to feed databases, without the need to spin up compute clusters, + or deal with Java class paths. + +In this spirit, LorryStream is effectively just a humble CLI interface for +Streamz. + +Telemetry readings +------------------ + + At my company, we use it at two different points in our data processing to + create a disjoint subcover of a noisy stream of telemetry readings and then + blend in metadata from users and external authoritative resources to give + users an understanding of what (and what kinds of) events are happening in + their space. + + +.. _CrateDB: https://github.com/crate/crate +.. _LorryStream: https://lorrystream.readthedocs.io/