You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by "pjfanning (via GitHub)" <gi...@apache.org> on 2023/09/06 17:27:11 UTC
[GitHub] [openwhisk] pjfanning opened a new issue, #5441: use Apache Pekko instead of Akka
pjfanning opened a new issue, #5441:
URL: https://github.com/apache/openwhisk/issues/5441
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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] style95 commented on issue #5441: use Apache Pekko instead of Akka
Posted by "style95 (via GitHub)" <gi...@apache.org>.
style95 commented on issue #5441:
URL: https://github.com/apache/openwhisk/issues/5441#issuecomment-1710501004
I am also interested in this issue.
@bdoyle0182 Do you mean we have to release the openwhisk 2.0 before migrating to Pekko?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk] bdoyle0182 commented on issue #5441: use Apache Pekko instead of Akka
Posted by "bdoyle0182 (via GitHub)" <gi...@apache.org>.
bdoyle0182 commented on issue #5441:
URL: https://github.com/apache/openwhisk/issues/5441#issuecomment-1710404641
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org