Hacker News Reader

It looks like a mixture between Akka (https://getakka.net/ less enterprisy than the Java version), which is based on the actor model and has a focus on distributed systems, and reactive libraries like rx (https://reactivex.io/). So maybe https://doc.akka.io/libraries/akka-core/current/stream/index... is the best fit.

View on HN

Worth mentioning Pekko, the Akka fork.

https://pekko.apache.org/

Is this an active fork?

In 2022 Lightbend relicensed Akka from Apache 2.0 to BSL, which was a huge problem for all of the other opensource projects (like Flink) that used it as part of their coordination layer. At this point most or all of them have moved to Pekko, which is a fork of the last release of Akka under Apache 2.0.

Seems like it based on GH activity, but I don’t know for sure.

https://github.com/apache/pekko

An important design consideration for Hydro, it seems, is to be able to define a workflow in a higher level language and then be able to cut them into different binaries.

Is that something Akka / RX offer? My quick thought is that they structure code in one binary.

Reply on news.ycombinator.com