Sometimes, I feel like Apache foundation is like Thanos, collecting all the distributed engines and watch the IT world burn.
From the beginning, Heron was envisioned as a new kind of stream processing system, built to meet the most demanding of technological requirements, to handle even the most massive of workloads, and to meet the needs of organizations of all sizes and degrees of complexity. Amongst these requirements:
The ability to process billions of events per minute
Extremely low end-to-end latency
Predictable behavior regardless of scale and in the face of issue like extreme traffic spikes and pipeline congestion
Simple administration, including:
The ability to deploy on shared infrastructure
Powerful monitoring capabilities
Fine-grained configurability
Easy debuggability
I can't wait for my next startup interview. We have a requirement of 25 messages per hour, with 10KB per message, you think you can build the ingestion pipeline using Kafka and MongoDB on a 10 node M5d.24xlarge cluster?
From the beginning, Heron was envisioned as a new kind of stream processing system, built to meet the most demanding of technological requirements, to handle even the most massive of workloads, and to meet the needs of organizations of all sizes and degrees of complexity. Amongst these requirements:
I can't wait for my next startup interview. We have a requirement of 25 messages per hour, with 10KB per message, you think you can build the ingestion pipeline using Kafka and MongoDB on a 10 node M5d.24xlarge cluster?