[akka-user] Re: "Event driven workflow engine" in Akka - any experiences?
See an example of distributed workflow (saga) implementation using akka-ddd (https://github.com/pawelkaczor/akka-ddd) framework: https://github.com/pawelkaczor/ddd-leaven-akka-v2/blob/master/headquarters/write-back/src/main/scala/ecommerce/headquarters/processes/OrderProcessManager.scala Best Regards, Pawel Kaczor -- >> 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-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Unimplemented deserialization of message with manifest issue
Issue created: https://github.com/EventStore/EventStore.Akka.Persistence/issues/28 Pawel -- >> 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-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: Unit test akka persistence against the inmem journal
This could be helpful: https://github.com/pawelkaczor/akka-ddd/blob/master/akka-ddd-test/src/test/scala/pl/newicom//test/dummy/DummyOfficeSpec.scala -- >> 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-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: The best ways to resolve future inside an actor?
I've just implemented something similar to allow Aggregate Roots collaborate with other Domain Service actors: https://github.com/pawelkaczor/akka-ddd/commit/4bb69eacb1cfe2ec108fbc2980e58e1da9a85bd0 I'm using tell (+ scheduled timeout) instead of ask. -- 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-user --- You received this message because you are subscribed to the Google Groups Akka User List group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: Can Cluster Sharding work across applications?
Hi Paul, if your frontend app is going to be deployed outside of the backend cluster you should consider use of Cluster Client (http://doc.akka.io/docs/akka/snapshot/contrib/cluster-client.html) together with Cluster Sharding. I use this pattern in akka-ddd project: https://github.com/pawelkaczor/akka-ddd/blob/master/akka-ddd-core/src/main/scala/pl/newicom//cluster/ShardingSupport.scala https://github.com/pawelkaczor/akka-ddd/blob/master/akka-ddd-write-front/src/main/scala/pl/newicom//writefront/GlobalOfficeClientSupport.scala On Friday, March 20, 2015 at 8:54:15 PM UTC+1, Paul Cleary wrote: I have two halves of an application, a front-end that is busy with ingesting data, and a backend for processing the data. Is it possible to have the front-end forward messages to the back-end using Cluster Sharding? I am interested in Cluster Sharding because I need to be able to have a single instance of an Actor in the entire cluster and refer to it by a logical name. Cluster Sharding seems like the way to go for this. Ideally, I could: --- http -- FrontEnd -- (look up actor via cluster sharding) -- BackEnd Actor Any ideas, or is Cluster Sharding intended to live inside the same app? -- 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-user --- You received this message because you are subscribed to the Google Groups Akka User List group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] AtLeastOnceDelivery - mapping my own messageId to deliveryId possible?
I created a ticket: https://github.com/akka/akka/issues/16874 and pull request: https://github.com/akka/akka/pull/16877 Cheers, Pawel -- 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-user --- You received this message because you are subscribed to the Google Groups Akka User List group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] AtLeastOnceDelivery - mapping my own messageId to deliveryId possible?
According to
http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#Relationship_between_deliver_and_confirmDelivery
: A function can be created to map your own messageId to deliveryId, which
may come from your own domain model. This function must keep track of which
messageId have been acknowledged. Alternatively, the Persistence module
provides a default sequence number implementation which can also be used as
the deliveryId for messages. The default sequence increases monotonically,
without gaps.
I would like to be able to use my own deliveryId. It is not possible with
current implementation (see code below).
trait AtLeastOnceDelivery {
private def nextDeliverySequenceNr(): Long = {...}
def deliver(): Unit = {
...
val deliveryId = nextDeliverySequenceNr()
...
}
}
Pawel
--
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-user
---
You received this message because you are subscribed to the Google Groups Akka
User List group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Akka Persistence - Views with multiple processors
On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote: The User actor persist FirstNameChanged, and inside the persist block it sends a Persistent(FirstNameChanged) message to the AllUsers Processor. On the query side we have a AllUsersView connected to that processor. When AllUsersView receives FirstNameChanged it updates the db table. To handle lost messages between User and AllUsers you might want to send an acknowledgement from AllUsers to User, and have a retry mechanism in User. I would implement that myself in User, but PersistentChannel might be an alternative. That is the most straight forward solution. The drawback is that FirstNameChanged is stored twice. What's wrong with the following (push only) solution (much more simple): User (eventsourced actor) reliable event delivery (Channel) --- AllUsers (normal actor, updates projection (i.e sql table)) Pawel -- 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-user --- You received this message because you are subscribed to the Google Groups Akka User List group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Akka Persistence - Views with multiple processors
On Friday, May 9, 2014 4:37:16 PM UTC+2, Olger Warnier wrote: On Friday, May 9, 2014 4:29:32 PM UTC+2, Paweł Kaczor wrote: On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote: The User actor persist FirstNameChanged, and inside the persist block it sends a Persistent(FirstNameChanged) message to the AllUsers Processor. On the query side we have a AllUsersView connected to that processor. When AllUsersView receives FirstNameChanged it updates the db table. To handle lost messages between User and AllUsers you might want to send an acknowledgement from AllUsers to User, and have a retry mechanism in User. I would implement that myself in User, but PersistentChannel might be an alternative. That is the most straight forward solution. The drawback is that FirstNameChanged is stored twice. What's wrong with the following (push only) solution (much more simple): User (eventsourced actor) reliable event delivery (Channel) --- AllUsers (normal actor, updates projection (i.e sql table)) Hi Pawel, In that way, you need to write your own mechanism to support replay towards the views. Kind regards, Olger Hi Olger, assuming update of projection is performed synchronously, confirmation will be sent back to User actor only after projection has been updated successfully. Events can be redelivered by User actor until they are confirmed (http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#Message_re-delivery) So, the reply towards the view mechanism is already available, just needs to be configured (max replies, restarts of User actor) ? Best regards, Pawel -- 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-user --- You received this message because you are subscribed to the Google Groups Akka User List group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
