Hi Johan,
Thanks for creating a small sample and nice logs. From that I can see and
understand what is going on.
In the second run the coordinator will use the same state as it had from
the first run, i.e. shard 0 is still allocated to the region actor known
from the first run. That specific acto
I looks like the TCK has not made it up to Maven-land yet, or is that just
me? I'm been looking
here: http://central.maven.org/maven2/com/typesafe/akka/
Incidentally, I've starting cobbling together a persistence plugin for
CouchDB, so I too will be sorting out handling json with Akka Serializ
I'm don't know of any implementations personally. It's not distributed
transactions though - it's a series of separate transactions and if there
is a rollback of the overall saga, compensating transactions are made to
reverse the initially committed transactions.
On Sunday, August 10, 2014 10:
None of this stuff is easy to do, and even harder to do right. Your post
gives away the main problem with getting this to work correctly, because
Actor Model and akka-persistence currently supports the first half of A,
but not the second half. In other words, to make the interface rich we not
o
We have an akka cluster with 10 nodes. it works almost smoothly except
periodic firing "Disassociated" WARN log, which seems cannot be recovered:
The following is the log records.
..
2014-08-10 00:00:09,253 WARN a.remote.ReliableDeliverySupervisor
akka.tcp://ClusterSystem@10.0.69.169:2551/
A few things I have noted when re-reading "Exploring CQRS and Event
Sourcing" http://msdn.microsoft.com/en-us/library/jj554200.aspx :
A. Events can play two different roles in a CQRS implementation: 1) Event
Sourcing - as a.p provides to persist the state of an aggregate root, and
2) Communica
Hi Garry,
Thanks for your points.
I am also working on solving this. Thinking of doing this via synchronous
communication between aggregate roots.
Is there a implementation of your idea and you are planning to put on GitHub?
Please share the details on thread.
Thanks a lot again ...it helped
Hi,
I understand.
But take my point of view...,,
thread had point discussed on sagas. I felt it's the perfect point to pitch in
my query as context was set.
If you have answer to my query please forward me to the thread.
Sent from my iPhone
> On 10-Aug-2014, at 21:07, ahjohannessen wrote:
>
Prakhyat, please stay on topic or start a new thread.
Thanks.
On Sunday, August 10, 2014 3:29:02 PM UTC+1, Prakhyat Mallikarjun wrote:
>
> Hi Gary/akka team,
>
> I have requirement in my app that changes to one aggregate root affects
> many more aggregate roots and all have to be in sync. I keep
Hi Prakhyat,
We are building a CQRS/DDD-oriented configuration system based on akka
persistence and are running into the same modeling issues. A few
characteristics of our specific case:
1) We do not expect a high volume of commands to be submitted (they are
generated via a task-based user inter
Hi Eric,
Thanks.Can you share any available implementation of this approach?
Is saga the only approach to solve this issue?
Also can we achieve or distributed transactions with different akka clusters
involved?
-prakhyat m m
--
>> Read the docs: http://akka.io/docs/
>>
Hi Eric,
Thanks.Can you share any available implementation of this approach?
Is saga the only approach to solve this issue?
Also can we achieve or distributed transactions with different akka clusters
involved?
-prakhyat m m
--
>> Read the docs: http://akka.io/docs/
>>
Hi Eric,
Thanks.Can you share any available implementation of this approach?
Is saga the only approach to solve this issue?
Also can we achieve or distributed transactions with different akka clusters
involved?
-prakhyat m m
--
>> Read the docs: http://akka.io/docs/
>>
Hi Eric,
Thanks.Can you share any available implementation of this approach?
Is saga the only approach to solve this issue?
Also can we achieve or distributed transactions with different akka clusters
involved?
-prakhyat m m
--
>> Read the docs: http://akka.io/docs/
>>
Hi Gary/akka team,
I have requirement in my app that changes to one aggregate root affects many
more aggregate roots and all have to be in sync. I keep seeing in discussions
name of sagas being refered. Will really sagas help to resolve this condition?
Can I find any articles in this regard?
A
How the performance of event sourcing will be impacted in a highly oltp
application which generates million of events?
There is a big overhead to store these events and also state of system in
durable db's for read or other purposes. Also don't you think event sourcing
apps will consume huge di
Hi Sean,
I was just reading through your discussions. I was quiet curious on how did you
measure message throughput in your app?
-prakhyat m m
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.h
Hi All,
I have a java client which is implemented to start a actorsystem and
connects to multiple remote akka clusters using Cluster Clients, it allows
users to execute queries passing a callback to get updates. The callback
doesn't hold any state/mutable data. But when the client execute a qu
Hi guys,
I've just started investigating akka stream module.
My use case is wrapping RabbitMQ worker queue with akka-stream (0.4). And
there might be many steps which required IO in a Flow. Potentially I could
put all of them into one function (with solution above) but will miss
stream "reacti
19 matches
Mail list logo
