[akka-user] Strategies to Track if a Message Has been Submitted?

Greetings, I have a situation where I have periodic tasks that will take several minutes. The manager will submit thousands of requests to a particular actor router. When the requests are received, They will be processed by the actor and completed. However, the scheduler has to run every

Re: [akka-user] Modeling synchronous startup behavior

Hi, In my system I have an initialization sequence that must take place at a certain order. Basically I don't want to open my system for incoming requests, before all services are properly started. So what I needed is sort of similar to what you describe here. I've implemented it without ask.

Re: [akka-user] Strategies to Track if a Message Has been Submitted?

A Bloom filter? On Tue, Oct 20, 2015 at 9:07 AM, kraythe wrote: > Greetings, > > I have a situation where I have periodic tasks that will take several > minutes. The manager will submit thousands of requests to a particular > actor router. When the requests are received, They

Re: [akka-user] Event-sourcing with aka-persistence

On Tue, Oct 20, 2015 at 8:26 AM, Adam Dohnal wrote: > You understand it right. Unfortunately, your solution won't work. Suppose > player has 30/100 health (current/max) and 99/100 experience and two > messages are sent to him with this order: > > AddExperience(10) >

Re: [akka-user] Capturing the message that killed an actor

Hi, when it comes to dealing with flow control, Akka Streams is unrivalled within Akka. On Mon, Oct 19, 2015 at 8:01 PM, Виктор Лобанов wrote: > Hi Viktor and Arne. > > Sorry for intrusion, but I have some thoughts about similar problem. > Recently I had similar design

Re: [akka-user] Re: Strategies to Track if a Message Has been Submitted?

Then you're basically down to a tradeoff in granularity of possible rework vs storage space / time: i.e. keeping track of highest-processed-contiguous-monotonically-increasing-task-id vs storing all messages and remove the ones which have been processed etc. On Tue, Oct 20, 2015 at 10:08 AM,

Re: [akka-user] Event-sourcing with aka-persistence

Interesting idea, thanks. But i'm afraid I will not recognise when my event stream is finished. I will try to think about it and redesign it to get an Observable which will be finite. If I succeed at it, I can simply convert that finite Observable to collection and persist that events But

Re: [akka-user] Akka remote communication roadmap?

Hi Roland, This is a very good and honest insight view of the Akka roadmap. You are doing an extreme good job with the Akka project. I hope the team will get bigger without compromising the quality. Best Regards. On 20 October 2015 at 11:13, Roland Kuhn wrote: > Guido, you

Re: [akka-user] Re: Akka remote communication roadmap?

If I have to give up on Akka remote because it is slow, I'll just switch to something like Vert.x, not sure what's going on here or why it has such little importance when it is part of Akka selling speech: "Location transparency" or is it only an advertisement but not used much in practice

Re: [akka-user] Akka remote communication roadmap?

Hi Roland, Fair enough, I agree with all you have said, specially the non-negotiable points which are the foundation of the remote communication contracts ported from Erlang paradigms, our application can survive with the times it has at the moment. I only needed to hear/know what you just

Re: [akka-user] Akka remote communication roadmap?

Guido, you are right that remote communication is key to what Akka is all about. The main hindrance in terms of implementation improvements is that there is a rather large complexity overhead incurred by supporting bidirectional TCP usage guaranteeing per-pair ordering with at-most-once

Re: [akka-user] Akka remote communication roadmap?

Thanks for your understanding, Guido. The offer of support is not specifically for you only, though: if anyone wants to start exploring this space then please go ahead and share your findings! Regards, Roland > 20 okt 2015 kl. 12:30 skrev Guido Medina : > > Hi Roland, > >

Re: [akka-user] Re: Proposed major simplification of the Akka Streams FlowGraph APIs

On Mon, Oct 19, 2015 at 12:51 PM, אדם חונן wrote: > "Makes sense, but once you do—is it a no-go or is there a means of doing > it?" > > Well, RxJava implements reactive streams, so obviously it's possible to do > the same things. > For example: > > For Broadcast, I'd use

Re: [akka-user] Akka remote communication roadmap?

HFT is really different I think,could not only depends on one framework to solve them all.Akka is really great ,as one of my mate said when he is reading ```java concurrency practice```,we would have failed without select Akka as our game server base. Akka/erlang or any other

Re: [akka-user] Akka remote communication roadmap?

Thanks, Filippo! Concerning reaching for other tools where appropriate: there is https://github.com/StefanE/AkkAeron but I have not yet tried it out—this might be a viable approach, too, that punts on location transparent ActorRefs in exchange for high

[akka-user] Re: Strategies to Track if a Message Has been Submitted?

Never heard of that. But false positives would be bad. From what i read the filter could produce those. On Tuesday, October 20, 2015 at 2:07:47 AM UTC-5, kraythe wrote: > > Greetings, > > I have a situation where I have periodic tasks that will take several > minutes. The manager will submit

Re: [akka-user] Event-sourcing with aka-persistence

You understand it right. Unfortunately, your solution won't work. Suppose player has 30/100 health (current/max) and 99/100 experience and two messages are sent to him with this order: AddExperience(10) TakeDamage(40) Correct behaviour is that first 10 xp is added to 109/100 ... level is

[akka-user] Example code of Servlet and Actor messaging each other

Does anyone know of some example code written in Java in which a servlet and an actor send messages to each other? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search

[akka-user] Re: Detecting Quarantined state

I'm also interested in this. Have you found a good solution besides doing string matching on the AssociationError exception message? Ideally there should be a named Exception to check for. Thanks, Gary On Wednesday, September 9, 2015 at 9:13:48 AM UTC-7, Chris Cheung wrote: > > How can I

[akka-user] Akka Cluster seed node config for restarts

I have a three-node cluster, nodes dnode0, dnode1, and dnode2. Every node the same seed node configuration as follows: akka { cluster { seed-nodes = ["akka.tcp://data@dnode0:2550","akka.tcp://data@dnode1:2550","data@dnode2:2550"] } } I first start all three nodes to form a

Re: [akka-user] Modeling synchronous startup behavior

This is definitely another option, but the object starting my actor is not an actor. I could possibly use inbox() to achieve a similar effect. I will think about it. Thank you. On Tuesday, October 20, 2015 at 3:23:07 AM UTC-4, Adam wrote: > > Hi, > > In my system I have an initialization

[akka-user] Akka Customers

Hello I am introducing Akka framework in my company and as part of presentation to Management, I have to add a slide telling them which companies are already using it. Is there a comprehensive list of customers who use Akka? Thanks very much + Harit Himanshu -- >> Read the

Re: [akka-user] Why is aroundReceive protected[akka]?

On Mon, Oct 19, 2015 at 3:42 AM, Patrik Nordwall wrote: > There is also the Receive Pipeline > http://doc.akka.io/docs/akka/2.4.0/contrib/receive-pipeline.html Oh, *neat* -- I've been wanting this for ages. Is this considered reasonably stable? At a quick look, I

Re: [akka-user] Why is aroundReceive protected[akka]?

I'm not sure how many people actually use it - we have not seen too many questions about it. Which either means it 'just works' or no-one is using it :-) If you'd like to give it a spin and provide feedback that'd be awesome! --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 21 October

Re: [akka-user] Cluster Sharding

Thank you so much Brice! Do you have a good design pattern for sending an init message to the new entity actor as soon as it is created? On Tuesday, October 20, 2015 at 1:36:51 AM UTC-7, Brice Figureau wrote: > > On Mon, 2015-10-19 at 21:03 -0700, vi...@eero.com wrote: > > In our

Re: [akka-user] Why is aroundReceive protected[akka]?

Okay -- it's on my to-do list. Which is about six miles long, so it may be a while, but I'll get to this eventually. The one great annoyance with using Requester is the need, under certain circumstances (specifically, when using stash()) to explicitly call its handler. (Which is automatically

[akka-user] Re: Akka Customers

http://www.typesafe.com/resources/case-studies-and-stories#filter:akka On Tuesday, October 20, 2015 at 8:55:16 PM UTC, Harit Himanshu wrote: > > Hello > > I am introducing Akka framework in my company and as part of presentation > to Management, I have to add a slide telling them which companies

Re: [akka-user] Modeling synchronous startup behavior

Well, for the integration points, assuming you need a response, uaing ask is a very good approach. I think the Play framework takes tgis approach. On Oct 20, 2015 10:40 PM, "Rich Henry" wrote: > This is definitely another option, but the object starting my actor is not > an

Re: [akka-user] Why is aroundReceive protected[akka]?

It's not in 2.3 /Patrik ons 21 okt. 2015 kl. 01:09 skrev Justin du coeur : > Okay -- it's on my to-do list. Which is about six miles long, so it may > be a while, but I'll get to this eventually. The one great annoyance with > using Requester is the need, under certain

[akka-user] Integration tests with Stubbed Cassandra

Dear group I am trying to implement some integration tests of my system using Stubbed Cassandra (to test what happens when requests time out etc). The problem is that Akka Persistence makes a lot of queries, and it would take a lot of priming for the stubbed Cassandra to behave like the real