
Cachely.dev
nxCloud
Apache Storm
Apache Spark
Apache Flink
Qubole
Hadoop
Google BigQuery
Apache Kafka
Amazon Kinesis
Cachely is the managed self-hosted remote cache for Nx and Turborepo - the cache backend you'd otherwise build and run yourself, hosted for you on Cloudflare's edge (R2). It's a drop-in replacement for a DIY @nx/s3-cache / S3 bucket setup: point your build tool at Cachely with a token and two environment variables, and share build cache across CI and every developer's laptop.
Unlike a self-hosted cache, Cachely enforces read-only tokens at the API, so pull-request and fork builds can read but never write - closing the Nx cache-poisoning attack (CVE-2025-36852). It adds ROI reporting (the real build minutes and dollars the cache saved), per-tool insights, and build-optimization suggestions on top.
Pricing is a flat per-workspace subscription with no per-seat fees - add every developer, bot, and CI actor without watching the bill. Cachely never stores your source code; it caches only task outputs and their content hashes. Nx and Turborepo today; Bazel on the roadmap.
Cachely.dev
Apache StormNo Cachely.dev videos yet. You could help us improve this page by suggesting one.
Based on our record, Apache Storm seems to be more popular. It has been mentiond 11 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.
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 / almost 4 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: almost 4 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
nxCloud - nxCloud is a commercial OwnCloud provider
Apache Spark - Apache Spark is an engine for big data processing, with built-in modules for streaming, SQL, machine learning and graph processing.