Use Cases

This section explores various use cases and applications for which Hotrod is well-suited for.

Ingestion

Hotrod can act as an ingestion layer for incoming data streams to perform filtering, sampling, pre-processing and data volume reduction, and then egress data into your existing systems, storage (on-disk, AWS S3, Azure Blob Storage), or your favourite analytics solution like Elastic Search, Scuba or Splunk.

Bridging

Hotrod can be deployed as a relay or a bridge that connects different systems, protocols and technologies. Use Hotrod as a bridge between HTTP services and Queues (AMQP, Kafka, NSQ), or turn static data sources (e.g. SQL sources) into data streams. Hotrod can even consume UDP and TCP data streams directly.

Collection

By co-locating Hotrod agents with other applications running on servers, Hotrod can collect and route metrics, logs and other data to different locations. Use Hotrod for log shipping, or to instrument systems that lack observability and telemetry mechanisms.

Monitoring

Hotrod has been successfully used by ISP's and MSP's to help solve network monitoring challenges. It's distributed architecture has allowed Hotrod to be applied to multi-site monitoring on private networks, to augment observability of SD-WAN solutions that lack instrumentation, to process and ingest large amounts of Netflow data, and to perform network traffic analysis and packet inspection at the edge.

Through any combination of ingestion, bridging and collection, Hotrod can be applied to help solve a wide range of simple or advanced data engineering challenges.