4 ms·

We're quite spoiled on the JVM when it comes to stream processing frameworks. Just a few off the top of my head: - Apache Spark (especially Spark Streaming) -

We're quite spoiled on the JVM when it comes to stream processing frameworks. Just a few off the top of my head: - Apache Spark (especially Spark Streaming) - Apache Flink - Apache Storm - Apache Apex - Apache Samza - Apache Ignite (also includes other things) and now Hazelcast Jet.

vegabook 10y ago
also, note Apache prepended every time. Can't help thinking there is concentration risk there.
- jonstewart 10y ago
  I'm hard-pressed to think of a feasible concentration risk for Apache projects. Can you be more specific?
  - vegabook 10y ago
    Flink, Spark, Samza, Kafka (Streams). All under the Apache umbrella. All doing similar things. Competitors. There is a risk of spreading resources too thin on the space, there is a risk that some of the projects will be guided towards sub-optimal objectives so as not to compete too directly with others projects in the portfolio, and there is clear branding dilution. This is made worse by the fact that all the projects use the JVM, eroding differentiation even further. And there is concentration risk for Apache making tons of bets in the same space as opposed to diversifying across sectors. Just a lay observation as I happen to have been perusing the space for a financial markets compute graph I am building, and was surprised by the lack of options outside of Apache, and in particular, away from the JVM.
    - lern_too_spel 10y ago
      Apache projects are independently managed, not by anybody paid by the ASF. https://community.apache.org/projectIndependence.html https://community.apache.org/projectIndependence.html
    - nl 10y ago
      Apache projects are often direct competitors. The Apache organisation is about good open source governance, not avoiding internal competition.
wsh91 10y ago
Apache Beam just got out of incubator, too, which means that there's now a low cost abstraction on top of two of those (as well as Google Cloud Dataflow). This stuff just seems to get better.

vegabook 10y ago

also, note Apache prepended every time. Can't help thinking there is concentration risk there.

jonstewart 10y ago
I'm hard-pressed to think of a feasible concentration risk for Apache projects. Can you be more specific?
- vegabook 10y ago
  Flink, Spark, Samza, Kafka (Streams). All under the Apache umbrella. All doing similar things. Competitors. There is a risk of spreading resources too thin on the space, there is a risk that some of the projects will be guided towards sub-optimal objectives so as not to compete too directly with others projects in the portfolio, and there is clear branding dilution. This is made worse by the fact that all the projects use the JVM, eroding differentiation even further. And there is concentration risk for Apache making tons of bets in the same space as opposed to diversifying across sectors. Just a lay observation as I happen to have been perusing the space for a financial markets compute graph I am building, and was surprised by the lack of options outside of Apache, and in particular, away from the JVM.
  - lern_too_spel 10y ago
    Apache projects are independently managed, not by anybody paid by the ASF. https://community.apache.org/projectIndependence.html https://community.apache.org/projectIndependence.html
  - nl 10y ago
    Apache projects are often direct competitors. The Apache organisation is about good open source governance, not avoiding internal competition.

wsh91 10y ago

Apache Beam just got out of incubator, too, which means that there's now a low cost abstraction on top of two of those (as well as Google Cloud Dataflow). This stuff just seems to get better.