pekko
zio-akka-cluster
pekko | zio-akka-cluster | |
---|---|---|
8 | 1 | |
1,074 | 164 | |
4.8% | 0.6% | |
9.7 | 0.0 | |
7 days ago | 13 days ago | |
Scala | Scala | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pekko
-
Is akka still worth learning to be employable?
Pekko is open source, has the same API. So there's no problem there.
- Migrate the classic transport of pekko to Netty 4 without CVEs
-
6 Common Misconceptions Around Akka-HTTP / Pekko-HTTP
Understandable considering the size of Pekko and how much time is passed, I would recommend asking any questions/concerns on either the Pekko mailing list https://lists.apache.org/[email protected] or on Github discussions https://github.com/apache/incubator-pekko/discussions.
-
Reconnecting with Scala. What's new?
Another big reason behind the "struggle" is we have done further improvements. For example the first release of Pekko will support all Scala versions from 2.12 up to 3.3.0 LTS (which was just released a couple of days ago). This also includes Pekko's modules which means we had to either add back in Scala 2.12 support or Scala 3 support. Yet another example would be https://github.com/apache/incubator-pekko/pull/281 which allowed us to drop scala-java8-compat dependency for Scala 2.13 or higher. So while these improvements aren't technically necessary, they have a large impact on Pekko going forward, i.e. the scala-java8-compat change means that we can drop Scala 2.12 at any point in time without breaking users.
-
Scala opensource projects
Apache Pekko is the open source fork of Akka. I know they can use more hands right now - https://github.com/apache/incubator-pekko/issues
-
What is the current status of Akka in your organisation?
There is an option missing: Considering switching to pekko when it's ready: https://github.com/apache/incubator-pekko
-
Stop Building on Corporate-Controlled Languages
- In 2022, Lightbend changed the Akka licence, made it proprietary and very expensive at large scale
Software that starts out as more "pure", non-corporate open-source can still turn the tables on you and charge large licensing fees later. But at least if it's open source from the start, it can be forked, e.g. for Akka, there's this Apache fork that was started after Akka changed its licence: https://github.com/apache/incubator-pekko . This is the key open source protection, and it's true for both corporate and non-corporate projects.
zio-akka-cluster
-
What is the current status of Akka in your organisation?
That has huge value and last time I checked there isn't any Scala ecosystem/software that can compete in this specific area. Even ZIO is just wrapping akka cluster (see https://github.com/zio/zio-akka-cluster).
What are some alternatives?
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
ZparkIO - Boiler plate framework to use Spark and ZIO together.
Scala Native - Your favorite language gets closer to bare metal.
grpc_bench - Various gRPC benchmarks
scala-cli - Scala CLI is a command-line tool to interact with the Scala language. It lets you compile, run, test, and package your Scala code (and more!)
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
tapir - Declarative, type-safe web endpoints library
nim-sqlite3-abi - SQLite3 wrapper
zio-saga - Purely Functional Transaction Management In Scala With ZIO
cask - Cask: a Scala HTTP micro-framework
zio-prelude - A lightweight, distinctly Scala take on functional abstractions, with tight ZIO integration