Steampipe
CloudQuery
StackQL.io
Turbot
OctoSQL
CloudRef App
CloudYali.io
Superintendent.app
Apache Storm
Apache Spark
Apache Flink
Qubole
Hadoop
Google BigQuery
Apache Kafka
Amazon Kinesis
Steampipe
Apache StormBased on our record, Steampipe should be more popular than Apache Storm. It has been mentiond 42 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
The request / data fetching is interesting in how "easy" it is to write. I did basic perusal of the examples, but I'd be interested to see what it looks like with rate-limited endpoints and concurrent requests. Another tangentially related project is https://steampipe.io/ though it is for exposing APIs via Postgres tables and the clients are written using Go code and shared through a marketplace. - Source: Hacker News / about 1 year ago
I really really like Steampipe to do this kind of query: https://steampipe.io, which is essentially PostgreSQL (literally) to query many different kind of APIs, which means you have access to all PostgreSQL's SQL language can offer to request data. They have a Kubernetes plugin at https://hub.steampipe.io/plugins/turbot/kubernetes and there are a couple of things I really like: * it's super easy to request... - Source: Hacker News / over 1 year ago
Https://steampipe.io/ showcases some really interesting scenarios for using FDWs in place of regular ETL and API integrations. - Source: Hacker News / about 2 years ago
Steampipe is a tool for querying cloud APIs and other data sources using SQL in a zero-ETL manner. - Source: dev.to / over 2 years ago
Few projects in the same realm that you should also checkout - [1] Steampipe (https://steampipe.io/) [2] InfraSQL (https://iasql.com/). - Source: Hacker News / over 2 years ago
There are several frameworks available for batch processing, such as Hadoop, Apache Storm, and DataTorrent RTS. - Source: dev.to / over 3 years ago
Although this article lists a lot of targets for technical selection, there are definitely others that I haven't listed, which may be either outdated, less-used options such as Apache Storm or out of my radar from the beginning, like JAVA ecosystem. - Source: dev.to / over 3 years ago
Storm, a system for real-time and stream processing. - Source: dev.to / over 3 years ago
Google has scaled well and has helped others scale, Twitter has always been behind by years. I think the only thing they did well was Twitter Storm, now taken up by Apache Foundation. Source: over 3 years ago
Streaming: Sparks Streamings's latency is at least 500ms, since it operates on micro-batches of records, instead of processing one record at a time. Native streaming tools like Storm, Apex or Flink might be better for low-latency applications. - Source: dev.to / over 4 years ago
CloudQuery - CloudQuery enables you to assess, audit, and evaluate the configurations of your cloud assets.
Apache Spark - Apache Spark is an engine for big data processing, with built-in modules for streaming, SQL, machine learning and graph processing.
StackQL.io - Query, provision, secure & operate cloud resources using SQL
Apache Flink - Flink is a streaming dataflow engine that provides data distribution, communication, and fault tolerance for distributed computations.
Turbot - Turbot's guardrails deliver automated operational, cloud security and cloud compliance controls of AWS deployments and other cloud enterprise infrastructure. Learn more.
Qubole - Qubole delivers a self-service platform for big aata analytics built on Amazon, Microsoft and Google Clouds.