GitHub user travissarles created a discussion: Strategy for gradual Akka → Pekko migration with shared library and rollback capability?
We're planning a gradual migration from Akka to Pekko and would appreciate guidance on the best approach. ## Our setup: - Multiple Scala 2.13 applications running as Docker images with Java 17 on Kubernetes - A shared internal library that currently depends on Akka and Akka Streams - All apps consume this common library ## Our goals: - Migrate to Pekko one application at a time in production - Maintain easy rollback capability (ideally by building both an Akka and a Pekko version of each app) - Avoid transitive dependency conflicts between Akka and Pekko artifacts ## What we've considered: - Using macros to switch imports between akka.* and org.apache.pekko.* - However, we suspect there might be a simpler or cleaner approach ## Our concerns: - Managing transitive dependencies when both Akka and Pekko artifacts could end up on the classpath - Security implications of whatever switching mechanism we adopt Has anyone implemented a similar incremental migration strategy? What patterns or tooling would you recommend for maintaining parallel Akka/Pekko builds during a transition period? Thanks in advance! GitHub link: https://github.com/apache/pekko/discussions/2592 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
