1. posterid:556830
  2. Heron

Re: Heron

Jonathan Boulle <jonathan.boulle@...>
 

I would echo Brian's sentiments - I also have some concerns about Heron's cloud-native suitability and path to integration with any of the existing or proposed CNCF projects; I think it's still hard for me to understand why we're a more suitable choice than Apache.

Alexis Richardson via cncf-toc <cncf-toc@...> schrieb am Fr., 17. März 2017, 11:56:

Moving Heron to new thread.

All - comments on Heron?  I think Brian raises some good questions
about alignment with our mission (below).




On Fri, Mar 17, 2017 at 3:56 AM, Quinton Hoole via cncf-toc
<cncf-toc@...> wrote:
..
> I don’t know enough about Heron and the related ecosystem to have an on that
> opinion yet.
>
> Q
>
> From:  Brian Grant via cncf-toc
....
> As for Heron, I'm not seeing the demand for Storm/Heron. For example, Google
> trends:
>
> https://trends.google.com/trends/explore?q=%2Fm%2F0ndhxqz,Apache%20Storm,%2Fm%2F0fdjtq
>
>
>
> Spark still has a lot of steam, and AIUI the trend (e.g., using Apache Beam)
> is towards unified batch and streaming.
>
>
>
> More broadly, though, I would like to see CNCF become a good home for
> container/orchestrator-friendly data-processing platforms, as that critical
> category of workloads benefits from closer integration with the underlying
> orchestration platform.
>
>
>
> --Brian
>
>
>
>
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
Join {cncf-toc@lists.cncf.io to automatically receive all group messages.