On Mon, May 11, 2015 at 12:22 AM, wrote:
> There seems to be no way to express this (simple) shape using a
> `FlexiRoute`. A naive version:
>
> class SplitShape[A](init: FanOutShape.Init[A] =
> FanOutShape.Name[A]("Split"))
> extends FanOutShape[A](init) {
>
> val whenTrue = newOutlet[A
Hi,
On Sun, May 10, 2015 at 11:31 PM, wrote:
> Hello,
>
> I have read all of the documentation. I am missing a simple overview that
> contains the different types of elements.
>
> As far as I can tell there are two things: Graph and Stage.
>
Not exactly. There are only Graphs with Shapes. Graph
I have a free open source prototype of a multi-agent system that learns and
forms plans by conversing with members of a community of Akka actors. -
each of which models the behavior of a different technology. Currently
coded in one language - Java. Scala would be coded also if interest shown.
I have developed a high-level library for efficiently setting up resilient,
fault-tolerant RabbitMQ consumers using Akka and Akka Reactive Streams.
Some of the features:
- Recovery:
- Consumers automatically reconnect and subscribe if the connection is
lost
- Messages published can opt
two link for the PDF
http://pages.cs.wisc.edu/~akella/CS838/F12/838-CloudPapers/FlumeJava.pdf
http://static.googleusercontent.com/media/research.google.com/zh-CN/us/pubs/archive/41378.pdf
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://do
My upcoming book "Reactive Messaging Patterns with the Actor Model"
discusses the use of PersistentView to support a Durable Subsriber.
On May 10, 2015 4:00 PM, "Alejandro López" wrote:
> @Olger Thanks for the detailed explanation of your approach. As Richard
> mentioned, it looks indeed like usi
There seems to be no way to express this (simple) shape using a
`FlexiRoute`. A naive version:
class SplitShape[A](init: FanOutShape.Init[A] =
FanOutShape.Name[A]("Split"))
extends FanOutShape[A](init) {
val whenTrue = newOutlet[A]("whenTrue")
val whenFalse = newOutlet[A]("whenFal
@Olger Thanks for the detailed explanation of your approach. As Richard
mentioned, it looks indeed like using persistent actor as durable queue.
Is there any concrete effort started already in the direction of supporting
this in Akka? Or at least there's some example implementations on this idea
Hello,
I have read all of the documentation. I am missing a simple overview that
contains the different types of elements.
As far as I can tell there are two things: Graph and Stage.
A graph has a `shape` which describes it's input's and it's outputs. There
are a few specialized shapes which a
Thank you VERY much Lutz, Patrik and Giovanni. This is very helpful.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka
Thanks. So I guess you're basically using a persistent actor as a durable
queue, in place of something like a Kafka topic, and a single message on
the queue can include ids of multiple aggregates.
On Sat, May 9, 2015 at 10:51 AM, Olger Warnier wrote:
> Hi Richard,
>
> I use the akka cluster shar
Hi All,
I have a graph consisting of 2 parts: The first part is a flow that
connects to an irc network, it looks something like this:
Source[IrcMessage, Unit]
The second part is a flow that is materialized once per client connection
(websockets: Flow[Message, Message, Any]).
The goal is to h
12 matches
Mail list logo
