use Apache Pekko instead of Akka

[pjfanning]

Most of the Apache Pekko jars are now released. A decent number of 3rd party libs now also support Pekko.

https://www.lightbend.com/akka/license-faq

[bdoyle0182]

I'll likely be the one that ends up tackling this once I have bandwidth. The hard part is new clusters will have to be formed so it's technically going to be a breaking changed. We've been planning a 2.0 release for a while with our new scheduling algorithm, we should probably revisit that.

[style95]

I am also interested in this issue.

@bdoyle0182 Do you mean we have to release the openwhisk 2.0 before migrating to Pekko?

[pjfanning]

The build dependencies in the OpenWhisk are quite dated.

• https://github.com/apache/openwhisk/blob/master/settings.gradle
• https://github.com/apache/openwhisk/blob/master/common/scala/build.gradle

Pekko is based off newer versions of the Akka libs. Also libs like Kamon have added Pekko support but only in more recent versions.

I think it would be a good idea to upgrade the existing dependencies to newer versions before trying to switch to Pekko. With Akka libs, I am suggesting latest Apache licensed versions - not the more recent versions that have Category X licenses.

• Akka 2.6.21 (due to CVEs)
• Akka HTTP 10.2.10 (due to CVEs)
• Akka Management 1.1.4
• Alpakka 3.0.1 (4.0.0 does not support Scala 2.12)
• Alpakka Kafka 2.1.1 (3.0.1 does not support Scala 2.12)
• Kamon 2.7.2
• spray-json 1.3.6
• logback 1.2.14 (due to CVEs)
• httpclient 4.5.14 (due to CVEs)
• netty 4.1.110.Final (due to CVEs)