-
Hi! 👋 I was playing with Jooby a little when I checked whether it was possible to leverage to an actor models like Akka, which would fit greatly in an event-driven software architecture. Looking on the official website, I've discovered there's an old Akka module, available only for the v1 version of Jooby. My questions are: is it possible to port it for the v2 too? Does it make sense with the current execution models available? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi, Glad you like Jooby. Guess it's possible, I didn't migrate bc no one asked until now (doubt how much people use it in 1.x) Would you like to submit a PR? If you do, you need to follow what is in the 3.x branch where basically each reactive library has his own module (rx, reactive, small rye). |
Beta Was this translation helpful? Give feedback.
-
I would be a little careful about including Akka anywhere in the codebase. A separate module living in its own repo is fine but it is sort of not entirely free anymore. Not really OSS. You can google around on it. Here is one link I found on it but there is plenty more: https://alexn.org/blog/2022/09/07/akka-is-moving-away-from-open-source/ Assuming one might be paying for Akka now I would delegate to lightbend on integrating since its their stuff now. I know @jknack is always very open to adding modules (he is practically a saint) to Jooby's core repo but I am not of the same opinion unless they are really useful and relevant (e.g. Jackson is fine but a different model of concurrency library that requires a different JVM language not so much). My reasons are:
|
Beta Was this translation helpful? Give feedback.
I would be a little careful about including Akka anywhere in the codebase. A separate module living in its own repo is fine but it is sort of not entirely free anymore. Not really OSS.
You can google around on it. Here is one link I found on it but there is plenty more:
https://alexn.org/blog/2022/09/07/akka-is-moving-away-from-open-source/
Assuming one might be paying for Akka now I would delegate to lightbend on integrating since its their stuff now.
I know @jknack is always very open to adding modules (he is practically a saint) to Jooby's core repo but I am not of the same opinion unless they are really useful and relevant (e.g. Jackson is fine but a different model of concurrency lib…