Based on our record, Materialize should be more popular than Apache Storm. It has been mentiond 72 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 2 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 2 years ago
Storm, a system for real-time and stream processing. - Source: dev.to / over 2 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 2 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 3 years ago
It's hard to write something that is both accessible and well-motivated. The best uses of category theory is when the morphisms are far more exotic than "regular functions". E.g. It would be nice to describe a circuit of live queries (like https://materialize.com/ stuff) with proper caching, joins, etc. Figuring this out is a bit of an open problem. Haskell's standard library's Monad and stuff are watered down to... - Source: Hacker News / 6 months ago
> [...] `https://materialize.com/` to solve their memory issues [...] Disclaimer: I work at Materialize Recently there have been major improvements in Materialize's memory usage as well as using disk to swap out some data. I find it pretty easy to hook up to Postgres/MySQL/Kafka instances: https://materialize.com/blog/materialize-emulator/. - Source: Hacker News / 6 months ago
I agree. So many disparate solutions. The streaming sql primitives are by themselves good enough (e.g. `tumble`, `hop` or `session` windows), but the infrastructural components are always rough in real life use cases. Crossing fingers for solutions like `https://github.com/feldera/feldera` to solve their memory issues, or `https://clickhouse.com/docs/en/materialized-view` to solve reliable streaming consumption.... - Source: Hacker News / 6 months ago
Or the related Materialize stuff https://materialize.com/. - Source: Hacker News / 7 months ago
The original post makes so much more sense in this context! One of the "holy grails" in my mind is making CQRS and dataflow programming as easy to learn and maintain as existing imperative programming languages - and easy to weave into real-time UX. There are so many backend endpoints in the wild that do a bunch of things in a loop, many of which will require I/O or calls to slow external endpoints, transform the... - Source: Hacker News / 7 months ago
Apache Spark - Apache Spark is an engine for big data processing, with built-in modules for streaming, SQL, machine learning and graph processing.
RisingWave - RisingWave is a stream processing platform that utilizes SQL to enhance data analysis, offering improved insights on real-time data.
Apache Flink - Flink is a streaming dataflow engine that provides data distribution, communication, and fault tolerance for distributed computations.
Google BigQuery - A fully managed data warehouse for large-scale data analytics.
Apache Kafka - Apache Kafka is an open-source message broker project developed by the Apache Software Foundation written in Scala.
Qubole - Qubole delivers a self-service platform for big aata analytics built on Amazon, Microsoft and Google Clouds.