Re: [akka-user] Re: Reactive applications with CQRS and Akka Persistence?

Hi Jeroen, On Friday, 27 June 2014 05:13:54 UTC+8, Jeroen Gordijn wrote: Why do you need a view that watches multiple Processors? This can already > be achieved. You create a child View for every Processor you would like to > watch. The child simply forwards all messages to its parent. > Ther

Re: [akka-user] Re: Reactive applications with CQRS and Akka Persistence?

Op maandag 23 juni 2014 15:27:38 UTC+2 schreef Ashley Aitken: > > > Sorry to bring this thread up again but I am still trying to work out the > read model in CQRS with Akka Persistence. > > On Tuesday, 6 May 2014 15:18:29 UTC+8, Martin Krasser wrote: >> >> >> The availability of (new) events i

Re: [akka-user] ̣̣[akka-stream] Looping or recusrion in Duct / Flow

Ok, thanks, I see. How should I feed my ActorProducer? It is a step of a Flow. Something like val myProducer = system.actorOf(...) Flow(ActorProducer[T](myProducer).map... Flow(...).foreach{ myProducer ! _ } ? Will the back pressure work between the two flows? Benoît Le mercredi 25 juin 2

Re: [akka-user] Re: AKKA 2.0-Message Delivery Gurantee-1 million SMS need to be sent

If at any point you catch yourself thinking "100%", re-read this post: http://aphyr.com/posts/288-the-network-is-reliable of multiple multiple failure examples with even redundant datacenter providers etc ;-) On Thu, Jun 26, 2014 at 8:24 PM, √iktor Ҡlang wrote: > I'd even take it a bit further

Re: [akka-user] Re: AKKA 2.0-Message Delivery Gurantee-1 million SMS need to be sent

I'd even take it a bit further and say that exactly once is not achievable (100%) in any distributed system as it is easy yo construe a situation which makes it impossible. On Jun 26, 2014 7:44 PM, "Filippo De Luca" wrote: > I believe that exactly one is something very difficult to achieve anyway

Re: [akka-user] Re: AKKA 2.0-Message Delivery Gurantee-1 million SMS need to be sent

I believe that exactly one is something very difficult to achieve anyway. But with Akka and ack messages you can achieve at-least-one that for an SMS is good enough. My 2cents On Jun 26, 2014 6:18 PM, "Ryan Tanner" wrote: > Akka offers only two guarantees: > > * At-most-once delivery. Each mess

[akka-user] Re: AKKA 2.0-Message Delivery Gurantee-1 million SMS need to be sent

Akka offers only two guarantees: * At-most-once delivery. Each message will be delivered either 0 or 1 times. There is no guarantee of exactly-once delivery. * Messages will be received in order for a given pair of actors. http://doc.akka.io/docs/akka/2.3.3/general/message-delivery-reliability

[akka-user] Re: Bounded mailbox for logging

In case you're using akka logging all messages will be published to the event bus . From this point they are sent as regular akka messages to the Slf4JLogger actor (if configured).

[akka-user] AKKA 2.0-Message Delivery Gurantee-1 million SMS need to be sent

This is Rajesh, Java Developer from Bangalore,India. I have a requirement of sending 1 million SMS's to the customer's.I was going through AKKA framework which I found as very interesting and promising.Can I use AKKA framework for my requirement?If yes how will AKKA guarantees a message deliv

Re: [akka-user] [Akka remote]

Hi Felipe,  I don't think that the script will add your lib directory to the class path automatically. You could either modify the script to do what you want, or take a look at the  sbt-native-packager that can package up your code together with your dependencies. B/ On 24 June 2014 at 04:58:

[akka-user] Re: akka-camel: support for using an external camel context (defined in spring xml)

Ok, I found it! http://doc.akka.io/docs/akka/2.3.3/scala/camel.html#CamelExtension and http://doc.akka.io/docs/akka/2.3.3/general/configuration.html#akka-camel "By Default, a new CamelContext

Re: [akka-user] Re: how to implement persistence actor?

Samples in order of my preference :-) Scala: https://github.com/akka/akka/blob/release-2.3/akka-samples/akka-sample-persistence-scala/src/main/scala/sample/persistence/PersistentActorExample.scala Java 8: https://github.com/akka/akka/blob/release-2.3/akka-samples/akka-sample-persistence-java-lambd

Re: [akka-user] Question about sent message from typedactor to untypedactor

What would the `unTypeActorProducer` do with the sender()? On Thu, Jun 26, 2014 at 11:01 AM, wrote: > Hi All, > > I need to send message from typedactor to untypedactor. But the > TypedActor.self() is not the type of ActorRef. So I can't write the code as > below. > Anyone know how to get the

[akka-user] Using actor state as a cache

Hi all, First of all a little bit of context. We are using akka and finagle to build a micro service framework to facilitate internal teams to bootstrap and create services. We are trying to build some cache mechanisms. One of the cache mechanisms is a simple in memory refreshable cache. When

[akka-user] Re: how to implement persistence actor?

sorry I am not familiar with scala. do you have the java version code? On Wednesday, June 25, 2014 7:07:53 PM UTC+8, ahjohannessen wrote: > > Here is an example of how you could store stuff in a list using a > persistent actor. > > class Example(id: String) extends EventsourcedProcessor { >

[akka-user] Question about sent message from typedactor to untypedactor

Hi All, I need to send message from typedactor to untypedactor. But the TypedActor.self() is not the type of ActorRef. So I can't write the code as below. Anyone know how to get the ActorRef of the TypedActor or how to let the untyped actor know which typedactor send the message? unTypeActo

Re: [akka-user] Re: resolve of path sequence failed

Thanks for reporting. Please add your stack trace to ticket https://github.com/akka/akka/issues/15440 If you have any hints of how to reproduce that is very welcome, and please add that to the ticket as well. Cheers, Patrik On Thu, Jun 26, 2014 at 9:58 AM, Carsten Saathoff wrote: > Hi, > > jus

Re: [akka-user] Re: resolve of path sequence failed

Hi, just for the record, I am also seeing the exact same problem with Akka 2.3.3. I also use the Cluster Sharding, and the events were stored with Akka 2.3.3 (it's a fresh setup from yesterday). This only happened after the system was under constant (but not excessively high) load. In between