-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove akka-zeromq module #15864
Milestone
Comments
This was referenced Sep 11, 2014
rkuhn
added a commit
to rkuhn/akka
that referenced
this issue
Sep 11, 2014
rkuhn
added a commit
that referenced
this issue
Dec 18, 2014
rkuhn
added a commit
that referenced
this issue
Jan 15, 2015
rkuhn
added a commit
that referenced
this issue
Jan 15, 2015
ktoso
pushed a commit
to ktoso/akka
that referenced
this issue
Feb 6, 2015
ktoso
pushed a commit
to ktoso/akka
that referenced
this issue
Jan 11, 2016
-zer akka#15864 remove zeromq module
asfgit
pushed a commit
to apache/bahir
that referenced
this issue
Nov 30, 2018
Initially, I just wanted to implement integration test for BAHIR-66. Google pointed me to JeroMQ, which provides official ZeroMQ binding for Java and does not require native libraries. I have decided to give it a try, but quickly realized that akka-zeromq module (transient dependency from current Bahir master) is not compatible with JeroMQ. Actually Akka team also wanted to move to JeroMQ (akka/akka#13856), but in the end decided to remove akka-zeromq project completely (akka/akka#15864, https://www.lightbend.com/blog/akka-roadmap-update-2014). Having in mind that akka-zeromq does not support latest version of ZeroMQ protocol and further development may come delayed, I have decided to refactor streaming-zeromq implementation and leverage JeroMQ. With the change we receive various benefits, such as support for PUB-SUB and PUSH-PULL messaging patterns and the ability to bind the socket on whatever end of communication channel (see test cases), subscription to multiple channels, etc. JeroMQ seems pretty reliable and reconnection is handled out-of-the-box. Actually, we could even start the ZeroMQ subscriber trying to connect to remote socket before other end created and bound the socket. While I tried to preserve backward compatibility of method signatures, there was no easy way to support Akka API and business logic that users could put there (e.g. akka.actor.ActorSystem). Closes #71
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in this roadmap update the ømq integration module is removed, it shall live on outside of the main Akka repository if there is enough public interest.
The text was updated successfully, but these errors were encountered: