Team,
We are building app on the approach DDD/CQRS/Event Sourcing.
Did you anytime have a look at this challenge
http://abdullin.com/post/dddcqrs-challenge-integrating-distributed-systems/
?
What are your thoughts and solutions? We are facing similar problem of
communicating across bounded c
Hi Björn,
Just to get more details about our approach from here:
We plan to use Akka Streams during communication with remote actors
(created through cluster aware routers). As of now communication with akka
remote actors is through netty protocol. Will netty communication work here
or we need
Getting there, it seems that one way to get something into DeadLetter is to
send a message to an actor that is stopped.
On Wednesday, September 24, 2014 2:48:13 PM UTC-7, Sean Shubin wrote:
>
> Found a clue, it seems to work as I had initially expected if I listen
> for UnhandledMessage instead
Thanks Jeroen, that helped me finally realize what I was misunderstanding.
Somehow it got stuck in my mind that the extracted id corresponded to the
persistence id, hence my confusion. Now, when I went back to the docs and
read it once more, the curtain lifted and I finally saw the comment in
Hi,
Since this is a breaking change in behavior, it can only be part of the 2.4
release and forward.
B/
On 24 September 2014 at 22:56:53, Mohnish Kodnani (mohnish.kodn...@gmail.com)
wrote:
To be more specific , will this change be available in 2.3.x codeline.
On Wednesday, September 24, 201
Hi Greg,
You're looking for:
import akka.pattern.pipe
class FooActor() extends Actor {
def receive = {
case inMsg:Msg => doSomeWork(inMsg) pipeTo sender() // doSomeWork returns
Future[Seq[String]]
}
}
I.e. you want to send the result of the Future, not the Future itself.
On Wed, Sep 24, 2014
Hello,
I have a remote actor that does work in its receive block that can return a
future. For example:
class FooActor() extends Actor {
def receive = {
case inMsg:Msg => sender ! doSomeWork(inMsg) // doSomeWork returns
Future[Seq[String]]
}
}
Would this work remotely? I tried using it
Found a clue, it seems to work as I had initially expected if I listen
for UnhandledMessage instead of DeadLetter. Perhaps I misunderstood
something from the documentation.
On Wednesday, September 24, 2014 11:25:27 AM UTC-7, Sean Shubin wrote:
>
> As far as I can tell from the documentation, th
To be more specific , will this change be available in 2.3.x codeline.
On Wednesday, September 24, 2014 1:23:31 PM UTC-7, Mohnish Kodnani wrote:
>
> Has this been released ?
>
>
> On Tuesday, April 1, 2014 12:27:36 PM UTC-7, Tyler C wrote:
>>
>> Awesome, thanks for the positive responses!
>>
>> J
Has this been released ?
On Tuesday, April 1, 2014 12:27:36 PM UTC-7, Tyler C wrote:
>
> Awesome, thanks for the positive responses!
>
> Just for the benefit of providing breadcrumbs, here's the ticket I created
> on Patrik's advice (you've probably seen it already).
> https://www.assembla.com/
Hi Björn,
Thanks again. I am bit clear now but still have some gaps.
[Björn]The persistent view is meant to be a view of the state built up from
the events of a persistent actor, not just a replication mechanism. As I
said in the other mail, if you only want to read the events, you can do
that
As far as I can tell from the documentation, this is the proper way to
listen for dead letters. Can anyone tell me why the "dead letter" event
seems to be ignored with this code? All it does is print the number 12345,
but I would expect it to also print the fact that it got a dead letter. My
é iniciado nessa classe actorconfig.java
package worker.calculator;
import akka.actor.ActorSystem;
import br.com.totvs.tfs.fees.util.ReadFileUtil;
import com.typesafe.config.Config;
import com.typesafe.config.ConfigFactory;
import core.SpringExtension;
import lombok.extern.slf4j.Slf4j;
import or
Hi Björn,
Thanks for replying. Here are some responses
*1) Are there many different routes that the messages can take to get to
the actor?*
Messages originate from various APIs that might involve delays (hence the
ordering problem). Once they reach the akka cluster, they are directly
routed to
I'm use the akka process in a web project with spring, i create a
akkaservletlistener where this start the process, the code is below, where
i put de activator?
package br.com.totvs.tfs.fees.web.servlet;
import akka.actor.Address;
import worker.calculator.BackendNodeStarter;
import worker.calcu
Hi Tiago,
>From your log you can see that the singleton is not running (or the proxy
>can't reach it), so the ClusterSingletonProxy has no one to talk to. You need
>to start whatever actor that you want to be a singleton by using the
>ClusterSingletonManager.
A nice Activator example is availa
Hi Prakhyat,
On 24 September 2014 at 11:33:57, Prakhyat Mallikarjun (prakhyat...@gmail.com)
wrote:
Björn,
Thanks for your insights. But Björn please help me with queries, I have too
many questions regarding behavior of PersistentView, its recovery and how its
lifecycle dependent upon Persist
Hi Prakhyat,
On 24 September 2014 at 14:51:06, Prakhyat Mallikarjun (prakhyat...@gmail.com)
wrote:
Team,
We are taking CQRS/DDD/Event sourcing approach to build our app.
Write side makes use of PersistentView to push events from write side to STATE
at read side.
If you only want to read th
Where do you create the ActorSystem in question?
Regards,
Roland
23 sep 2014 kl. 16:10 skrev Tiago Canatelli :
> Thanks a help, the problem is solution
>
> Em sexta-feira, 19 de setembro de 2014 08h59min17s UTC-3, Tiago Canatelli
> escreveu:
> Bom dia pessoal,
>
> estou iniciando no desenvol
+1
On Wed, Sep 24, 2014 at 5:07 AM, Endre Varga
wrote:
> There will be all kinds of merges available in the future. Akka Streams is
> still a preview so we change stuff all the time. To get to the point where
> we can support pluggable merges we needed the graph API and support for
> n-way fan-i
I'm working a little time with akka, i get a problem to solution because i
don't has a good support here, then a resolve post this forum
2.3.6
Cluster start correctly
Is the cluster singleton running in the cluster? -> Wha is this?
When the message sended, i have this log:
[DEBUG] [09/24/2014 10
Team,
We are taking CQRS/DDD/Event sourcing approach to build our app.
Write side makes use of PersistentView to push events from write side to
STATE at read side.
But this happens asynchronously as PersistentView pulls events from its
PersistentActor
at configured interval. The PersistentVie
Hi,
Your mail has a lot of information but I still need some more information.
Which version of akka are you using?
Does the cluster start up properly? Is the cluster singleton running in the
cluster? Do you see any errors in the logs?
If you don't use the custom serializer, do you still have
Hi,
I don't completely understand how you have designed your system or why you
have/think you have a problem.
If there is one actor representing the Amount in your table, and all requests
to change the amount go through that actor, then the requests will happen one
after each other.
This mean
Björn,
Thanks for your insights. But Björn please help me with queries, I have too
many questions regarding behavior of PersistentView, its recovery and how
its lifecycle dependent upon PersistentActor. I tried a lot to find
documentation, but there is no detailed explanation anywhere.
I und
There will be all kinds of merges available in the future. Akka Streams is
still a preview so we change stuff all the time. To get to the point where
we can support pluggable merges we needed the graph API and support for
n-way fan-in operations first. So stay tuned :)
-Endre
On Wed, Sep 24, 2014
Hi Prakhyat,
On 23 September 2014 at 14:28:18, Prakhyat Mallikarjun (prakhyat...@gmail.com)
wrote:
Team,
I am not able to thoroughly understand Behavior Of PersistentView . I have
below queries,
1. How does PersistentView works?
The name PersistentView is somewhat misleading. It is a not a
Hi Neeraj,
On 24 September 2014 at 08:10:58, tomerneeraj (tomer.nee...@gmail.com) wrote:
Hi,
We developed our application on Akka (2.3.4). We are running 5 nodes in Akka
Cluster where we are using cluster aware routers to distribute the traffic.
Application seems to be worked fine when traffic
28 matches
Mail list logo
