[akka-user] Re: Memory Bounding Akka Streams

THANK YOU for your responses; and very helpful Endre to explain! Need to Google up those JS interfaces for async and sync! So, then, if you've got a system of remote services talking to each other; you pretty much need to be coding to interfaces which support the Reactive protocol on (both)

[akka-user] Re: Memory Bounding Akka Streams

> > LATEST updated understanding I have then is the following; and happy for > anyone to correct my (Newbie) understanding with a link to a clear Blog > Post or GitHub repo illustrating this concept! > > I had got this information from the excellent Manning book, 'Akka In > Action'. That

[akka-user] Re: Memory Bounding Akka Streams

Akka Streams has several stages that backpreassures on different conditions, as you can see here . As far as I know, there is no built-in stage that backpreassure when a number of bytes are buffered. The buffer stage you

[akka-user] Re: Memory Bounding Akka Streams

OK Victor Klang: would you please be so kind as to elaborate with some helpful details on your prior reply? ;0) 1) My reading of the docs is that the '.buffer' API is necessary to handle the case where if the Source streams data faster than the Sink can handle it; then one can run into 'Out