|
|
|
|
|
by edejong
1690 days ago
|
|
In the past I have designed, implemented and brought into production many Akka based systems with medior and senior teams. Most of these were akka-streams based. The Akka actor model requires a different mode of thinking which can cause problems for experienced engineers. Ideas such as 'let it crash' and at-most-once-delivery are not trivial. Basically systems design based on resilience instead of robustness. When Actor based systems are well designed, they can be extremely powerful, scalable, resilient and adaptable. Small nitpick. I found that akka-streams missed many useful primitives. For our toolkit, I designed flows with retry-logic, flows with cache lines and flows with metric measurements (sending data to Datadog). |
|