JStorm: Alibaba's Storm Fork When the In-House Stream Had to Outrun the Upstream
How Alibaba forked Apache Storm into JStorm to get a faster, more operable stream processor for commerce and logging pipelines at internal scale.
Tag
5 articles · 18 min of reading
How Alibaba forked Apache Storm into JStorm to get a faster, more operable stream processor for commerce and logging pipelines at internal scale.
How Confluent's ksqlDB turned Kafka topics into tables and streams you can query with SQL, and why event-time windows still leak through the syntax.
How Netflix built Keystone, its Kafka- and Flink-based real-time data platform, and why it later migrated the processing layer from Samza to Flink.
Why Twitter replaced Apache Storm with Heron, a re-architected stream processor with per-task process isolation and built-in backpressure.
How LinkedIn built Apache Samza to pair with Kafka, using partitioned logs and local state to make stateful stream processing durable and rebalanceable.