These are chat archives for akkadotnet/AkkaStreams

23rd
Nov 2016
alexeykap
@alexeykap
Nov 23 2016 11:58
Hi all. I have question about akka.Streams. Is it possible to send data for exampe string array from one ActorSystem to another using streams?
Bartosz Sypytkowski
@Horusiath
Nov 23 2016 12:36
@alexeykap akka streams by default are optimized for locality, so your stream/graph will be placed inside a single process. You may however define explicit endpoints, as i.e. ActorPublisher or even ordinary actor may be used as a source or a sink
(in case of actors however you'd need to assure that messages won't be lost, otherwise your stream may end up in deadlock)
alexeykap
@alexeykap
Nov 23 2016 13:08
@Horusiath thx
Boban
@bobanco
Nov 23 2016 13:12
@Horusiath any plans on porting Gearpump, i could help porting the transport layer with DotNetty
Bartosz Sypytkowski
@Horusiath
Nov 23 2016 13:32
@bobanco getting into consideration, that this is my homework project, I must be careful with making another akka plugin ;) Porting is easy, but then we need someone to provide support and maintain it ;)
I'd love to work on gearpump imho, but we also need to focus on hardening existing plugins
i.e. right now I'm optimizing SQL backend for akka.persistence (I've got 10x improvement so far :P )
@AaronontheWeb @Silv3rcircl3 @alexvaluyskiy what are your opinions? Are we ready to start porting gearpump (Akka.Stream materializer for distributed graphs)?
Boban
@bobanco
Nov 23 2016 13:44
@Horusiath good to know, well done man :+1: , regarding gearpump i could start porting the transport and the clustering part trough this weekend
after that you or anyone who is willing to contribute can carry on
Bartosz Sypytkowski
@Horusiath
Nov 23 2016 13:45
sounds cool. We could probably build a separate branch (maybe even the project) for it. The last time I've checked, gearpump incubator was not fully akka.streams compatible and it had some work going of gearpump/akka-streams branch
Alex Valuyskiy
@alexvaluyskiy
Nov 23 2016 19:09
@Horusiath I think it does not make any sense to port Gearpump right now, because Akka Streams on .NET doesn't have a big adoption
Only 4 downloads per day
We should work on that first
Marc Piechura
@marcpiechura
Nov 23 2016 20:26
@Horusiath @bobanco @alexvaluyskiy Maybe the adaption would be higher if we would have distributed streams because many request are exactly about that. But I don't see how we could handle the work. We are already 3 versions behind the jvm again and have the work for Alpakka.
if @bobanco would like to do it and maintain it I'm happy to guide and review the work but I don't think we have the resources to do this with the current manpower
Marc Piechura
@marcpiechura
Nov 23 2016 21:19

@Horusiath regarding FileIO.ReadAllLinesnot sure if we need it as API since it's already quite easy to archive via Framing helper stage

System.IO.File.WriteAllText(createdFile, "test\r\nnew line\r\nanother new line");

var result = FileIO.FromFile(new FileInfo(createdFile))
        .Via(Framing.Delimiter(ByteString.FromString("\r\n"), int.MaxValue, true))
        .Select(b => b.DecodeString())
        .RunWith(Sink.ForEach<string>(Console.WriteLine), Materializer);

and for Source.Empty
wouldn't this have the same effect ?

Source.Empty<int>().MapMaterializedValue(_ => 42);
Bartosz Sypytkowski
@Horusiath
Nov 23 2016 21:42
@Silv3rcircl3 I know, this is just to make like easier ;)
Marc Piechura
@marcpiechura
Nov 23 2016 22:16
I see
so yeah why not, add them if you want ;)
Marc Piechura
@marcpiechura
Nov 23 2016 22:34
And btw couldn't we use "dynamic" to get rid of IUntypedPublisher/Subscriber ? Also would that maybe help for TMat ? I know we had some problems with it but I can't remember which exactly
Bartosz Sypytkowski
@Horusiath
Nov 23 2016 22:36
I'm fine with anything that will make it simpler without loosing performance