[akka-user] [streaming] newbie Q's about time and scale

Hi. I'm recently read about reactive streams, and want to know some more about it. In particular I was trying to use the 'Flow' methodology to replace some existing log-analysis software, which does things like page views, unique visitors and things like that in 5 minute blocks. It looks quite sim

Re: [akka-user] How to Store the Message Object/Class to a database?

Glad I could help! Happy hakking! --  Konrad 'ktoso' Malawski hAkker @ typesafe -- >> 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

Re: [akka-user] How to Store the Message Object/Class to a database?

Wow! I didn't know akka-persistence. Thank you Konrad! Akka is very very powerful. On Thursday, May 29, 2014 11:22:21 AM UTC-4, Konrad Malawski wrote: > > Hello Allen, > have you had the chance to look into our > akka-persistencemodule?

Re: [akka-user] AOP in Akka

Hello Leon, Well, "the Scala way"™ would rather be using plain total or partial functions and composing them - I believe that's what whoever the quoted sentence comes from had in mind. In Akka we also believe that less magic is better :-) I would therefore suggest you to try modelling your require

Re: [akka-user] How to Store the Message Object/Class to a database?

Hello Allen, have you had the chance to look into our akka-persistence module? Apps like you describe are very nicely modelled as events and “opposite events” if you want to “undo”. And direct answers to your questions: - path - the a

Re: [akka-user] Is ask an anti-pattern in akka actors?

Thanks it makes perfectly sense, it was my feeling. On May 28, 2014 4:28 PM, "Heiko Seeberger" wrote: > Actor selection essentially is look up and we all know that look up should > not be overused. It has it’s purpose though, e.g. when you want to connect > to a remote system (How would you get a

Re: [akka-user] supervisor hierarchies

Thanks Conrad I understand. I think understanding the "error kernel pattern" is really important together with http://doc.akka.io/docs/akka/2.3.3/general/actor-systems.html of the documentation. On Thursday, 29 May 2014 11:48:28 UTC+1, Konrad Malawski wrote: > > Not "exactly one", but yeah "a

[akka-user] Re: Unable to test `Processor` and `EventsourcedProcessor` with `CallingThreadDispatcher`

Ah yes, I had forgot to remove that! Good suggestion on using self-typing to abstract-away implementation detail :D The code is looking a lot better now guys, and there's no funny business! Thanks! -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ:

Re: [akka-user] supervisor hierarchies

Not "exactly one", but yeah "as little as possible". This way of thinking will force your thinking towards creating these hierarchies of actors which fail or survive together (kind of like the four musketeers :-)). And the gains have been outlined already - you are able to fail / restart / isolate

Re: [akka-user] Unable to test `Processor` and `EventsourcedProcessor` with `CallingThreadDispatcher`

I may have answered my own question: Scala Mixins! trait ChecksEmailAddressAvailability extends Actor { val emailCredentialsView: ActorRef protected def checkEmailAddressAvailability(emailAddress: EmailAddress)(block: Boolean => Unit)(implicit context: ActorContext): Unit = { queryAva

Re: [akka-user] supervisor hierarchies

Hello Konrad, I had read the relevant documentation but I still couldn't work out the structure of the actor hierarchies. Does this mean that there you should only have one actor which is the child of the user guardian, or am I missing something? On Wednesday, 28 May 2014 23:24:08 UTC+1, Konr

Re: [akka-user] akka cluster connection refused

You have seed-nodes setting pointing to other node in the cluster. So naturally when you first start either node it tries to connect to the other one which has not been started yet. Thus the log message: Reason: Connection refused: /10.xxx.xxx.xxx:15672 You can choose which node you want to start