guardian / guardian/dotcom-rendering

Akka migration

Open
#8,783 1 comment 0 reactions 1 assignee Claimed by @DanielCliftonGuardian View on GitHub
Dominant language
TypeScript
Stars
274
Forks
34
Avg merge
2d 22h
Merged PRs (30d)
121

Description

What do I need to do?

- Read the background in our [doc](https://docs.google.com/document/d/1gGYkt7OspuT_g2aQejJ4lNPUL3LtmeEywE-hbiP6lLQ/edit)
- Understand your usage (see the [dashboard](https://metrics.gutools.co.uk/d/uHqcUJXVz/akka-usage?orgId=1&var-peteam=Operations%20Tools%20and%20Infrastructure))
- Share any issues/experiences in [this spreadsheet](https://docs.google.com/spreadsheets/d/1t51M3QNuw2TJF8FASDc1CyiIreofKgMk8f4PiXARa8A/edit#gid=0) and also in [#DevX Stream](https://chat.google.com/room/AAAAag0I08g?cls=7).
- Pekko migration guide https://pekko.apache.org/docs/pekko/current/project/migration-guides.html

Looking at Akka usage via import statements it seems that we should be able to ignore uses of import akka.stream.Materializer based on what is allowed usage from the doc.
```[tasklist]
### Tasks
- [x] Replace import akka.actor.ActorSystem with import org.apache.pekko.actor.ActorSystem (draft PR introducing pekko here https://github.com/guardian/frontend/pull/26563)
- [x] Replace import akka.util.Timeout with org.apache.pekko.util.Timeout
- [x] Replace akka.pattern.CircuitBreaker with org.apache.pekko.pattern.CircuitBreaker, import akka.pattern.after, akka.pattern.CircuitBreakerOpenException, import akka.pattern.{ask, pipe}
- [ ] Update akka config for each application
- [ ] Rename uses of akkaAsync to pekkoAsync to make it clear which library this uses
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.