pekko VS Play

Pekko is open source, has the same API. So there's no problem there.

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.

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.

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

There is an option missing: Considering switching to pekko when it's ready: https://github.com/apache/incubator-pekko

- 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.

My major complain here is that, as far as being a web framework there is precious little information here about the framework. How does this framework scale with multiple requests? What concurrency strategy is it using (threads, processes, actors, etc?). Is this opinionated (it doesn't seem so but it also doesn't say it isn't either). How does this work with popular libraries x,y,z. The full docs have a little bit more information, but not a ton. But mostly there are some cute toy examples and "built in python" and thats about it.

Lets compare this with for example play https://www.playframework.com/ I know from this that it built on Akka, its stateless, aims for predictable resource consumption, has non-blocking io, etc. There is a ton of really important information on what does this web framework actually do that is really important when you are making a choice of a framework.

I have no idea how good this framework is, but besides a few toy examples, I can't see anything that makes me thing "wow this is great I need to use this".

A web application framework for Java/Scala: https://www.playframework.com/

Scala 3 migration isn't as simple as migrating other apps, you can track the work at https://github.com/playframework/playframework/issues/11260

And there are frameworks you can use to make development easier, like Play. And Java has plenty of choices for dependency injection frameworks.

However do note, Play should be perfectly usable as well, and it's still maintained by the community: https://github.com/playframework/playframework/issues/11649

In university I learned a bit of Java, so maybe I could use it professionally I guess?. There were many options to choose from. DropWizard, Spark, Play Framework. But the more documented one in the internet I found was Springboot, besides there were some courses in spanish and some friends that knew something about Springboot, so I give it a chance.

For a backend web server I use Play - https://www.playframework.com/ which I find to be the easiest one as a backend web server. For learning/using spark I found this course from coursera to be very useful. https://www.coursera.org/learn/scala-spark-big-data