Skip to content
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

If ActorPublisher/Subscriber are to be deprecated what is the recommend approach? #3670

Open
acds opened this issue Dec 7, 2018 · 0 comments

Comments

@acds
Copy link

acds commented Dec 7, 2018

Per:
https://getakka.net/articles/streams/integration.html#implementing-reactive-streams-publisher-or-subscriber

WARNING
ActorPublisher class and ActorSubscriber class will probably be deprecated in future versions of Akka.

What is the recommended approach?

One tends to want to wrap a source resource up in an Actor (say to call a REST API that returns batches of results) and pipe those results into a stream, but have back pressure to only get the next batch when down steam can handle them.

The WebCrawler sample uses the Actor as a Coordinator but then you lose out on the Actor wrapping the source on its own so you break your API encapsulation.

Also much of the documentation related to article that is linked in issues related to Streams, or on the Petabridge site seem to be broken.

Thanks for any insights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant