Similar to [[Apache Kafka]] and [[Redpanda]]. You can put logs in it. Route it with [[Vector]] or [[Benthos]]. I suppose it uses a [[Publish–subscribe pattern]]. Hook it up with [[Amazon Kinesis Data Firehose]]. Imagine Jeff Bezos holding a firehose, sending your data out from the stream to whatever location you choose. Read [SQS or Kinesis? Comparing Apples to Oranges](https://sookocheff.com/post/aws/comparing-kinesis-and-sqs/). > When AWS announced Kinesis we saw something that gave us everything we’d get from Kafka, plus [resharding](http://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-scaling.html) and zero system maintenance! Kinesis would also cost substantially less than both our historical system and alternative replacement systems. We’ve been running Kinesis in our production environment for a while now, and have been thrilled with the results. > Kafka is often used for operational monitoring data. This involves aggregating statistics from distributed applications to produce centralized feeds of operational data. > Many people use Kafka as a replacement for a log aggregation solution. Log aggregation typically collects physical log files off servers and puts them in a central place (a file server or HDFS perhaps) for processing. **Kafka abstracts away the details of files and gives a cleaner abstraction of log or event data as a stream of messages. This allows for lower-latency processing and easier support for multiple data sources and distributed data consumption.** In comparison to log-centric systems like Scribe or Flume, Kafka offers equally good performance, stronger durability guarantees due to replication, and much lower end-to-end latency. ## Kinesis Use Cases - Log and Event Data Collection - Real-time Analytics - Mobile Data Capture - “Internet of Things” Data Feed