[akka-user] Event sourcing template

I'm excited to see the new cluster-sharding activator template, which I think might address some of the confusion I've had about eventsourced DDD with an actor per aggregate root. Do I understand correctly that the actual instantiation of the Post processor actor is something that happens within

[akka-user] Re: Event sourcing template

to think of actors as entries rather than workers. On Fri, Feb 21, 2014 at 12:28 PM, Richard Rodseth rrods...@gmail.comwrote: I'm excited to see the new cluster-sharding activator template, which I think might address some of the confusion I've had about eventsourced DDD with an actor per aggregate

Re: [akka-user] Re: Event sourcing template

at 2:54 PM, Patrik Nordwall patrik.nordw...@gmail.comwrote: Hi, On Fri, Feb 21, 2014 at 10:42 PM, Richard Rodseth rrods...@gmail.comwrote: I have now read the sharding documentation, and this in the template. Sorry I jumped the gun in my excitement :) To send messages to the identifier

[akka-user] Event Sourcing and Versioning

Now that we're getting excited about using akka persistence for event-sourced DDD applications, can anyone provide any insights or resources about handling versioning? Anything specific to akka persistence? For example I have a book (produced by Microsoft) that talks about mapping/filtering events

[akka-user] TCP

I've never done any sort of TCP protocol implementation, and am looking at Akka IO for this purpose. I noticed here: http://hseeberger.github.io/blog/2013/06/17/introduction-to-akka-i-slash-o/ that the handler actor calls context.watch() // We need to know when the connection dies without

[akka-user] Re: TCP

Bumping this, but I'll add a question about backpressure. For a new TCP project, would you still recommend Akka IO over say Akka + Netty given that Pipelines is deprecated and reactive streams is not ready? On Fri, Mar 21, 2014 at 8:42 PM, Richard Rodseth rrods...@gmail.com wrote: I've never

Re: [akka-user] DDD/Eventsourcing with Akka Persistence

Take a look at the cluster sharding activator template, and some of the answers to my questions on this group. I think it would be nice to have an Activator template for DDD/Akka Persistence that didn't depend on a cluster. On Mon, Apr 14, 2014 at 9:46 AM, Jakub Czuchnowski

Re: [akka-user] What is the best way to integrate kafka and akka

Here's the Kafka TCP protocol https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol I believe they're re-doing the high-level consumer and produce APIs as we speak. On Mon, Apr 14, 2014 at 1:14 PM, Scott Clasen scott.cla...@gmail.comwrote: Im actually working on an

Re: [akka-user] Re: TCP

Exciting news. At this point I'm an interested bystander, but I'll be watching closely and hopefully getting my hands dirty in the not too distant future. Thanks for the update. On Thu, Apr 17, 2014 at 5:08 AM, Akka Team akka.offic...@gmail.com wrote: Hey there :-) This has been left

[akka-user] Work Pull Pattern

I'm implementing this pattern using Michael Pollmeier's contribution: https://github.com/mpollmeier/akka-patterns and have run into some problems along the way. The first was my error. I overrode the iterator with a def instead of a val, and as a result the Master never advanced through the Epic

[akka-user] Futures/Actors, Ask/Tell and the (JDBC) blocking problem

I realize this is well-trodden ground, but it's still a bit confusing for newcomers. Can we agree that the ask pattern is legitimate at the boundary between a service and repository/DAO? It seems to me that it is reasonable to want to abstract away the persistence layer in a way that doesn't

[akka-user] Killing a blocked actor

Not sure if this is the right approach, but I have the makings of a little REPL as shown below (I know this guy will need a dedicated dispatcher). The idea is that console input, including exit is sent to the parent which would like to do a graceful shutdown. Is there a way in the parent to kill

[akka-user] Actor lookup design

I'm having an absolute blast building my first non-trivial actor system, and learning a lot. Kudos to the team. The tool needs to access different database environments, depending on user input. In order to manage blocking, I have a Database actor which is initialized with a DatabaseRef, and has

[akka-user] Re: Actor lookup design

I see here that I can do context.child(name) http://grokbase.com/t/gg/akka-user/138x5t8xbz/referencing-actor-from-map-string-actorref-vs-referencing-from-path On Sat, Jun 28, 2014 at 4:08 PM, Richard Rodseth rrods...@gmail.com wrote: I'm having an absolute blast building my first non-trivial

[akka-user] Future[Option[T]] and pipeTo self

So I've run into the Monads don't compose problem and am a bit reluctant to tackle monad transformers and Scalaz at this point. I'm wondering what you all think about mapping the Future[Option[T]} to something like Future[MyMessageType] , piping to self, and then pattern matching on

Re: [akka-user] Future[Option[T]] and pipeTo self

(it just gets a None, it doesn't even know what Option[T] it was since the T is erased.) What's the use-case? On Sun, Jun 29, 2014 at 3:34 AM, Richard Rodseth rrods...@gmail.com wrote: So I've run into the Monads don't compose problem and am a bit reluctant to tackle monad transformers

Re: [akka-user] Future[Option[T]] and pipeTo self

in the algebra (which I'd prefer). On Sun, Jun 29, 2014 at 3:40 PM, Richard Rodseth rrods...@gmail.com wrote: Hi Viktor The use case is an actor that processes commands, creating jobs. But first it has to look up something in the database to send to the job along with the other job parameters

Re: [akka-user] Killing a blocked actor

viktor.kl...@gmail.com wrote: Also relevant: https://groups.google.com/forum/#!topic/scala-user/52bq9s1JNY0 On Mon, Jun 30, 2014 at 3:45 PM, Patrik Nordwall patrik.nordw...@gmail.com wrote: On Thu, Jun 26, 2014 at 5:58 AM, Richard Rodseth rrods...@gmail.com wrote: Not sure

[akka-user] Work push/pull vs ?

I've had some success using the worker pull pattern to process time series data in a particular channel. A channel job actor builds the queue of time chunks for a work pull master and workers work on chunks of time. Now I wish to process multiple (possibly millions of) channels in parallel and

[akka-user] Re: Work push/pull vs ?

being dense. On Tue, Jul 1, 2014 at 6:08 PM, Richard Rodseth rrods...@gmail.com wrote: I've had some success using the worker pull pattern to process time series data in a particular channel. A channel job actor builds the queue of time chunks for a work pull master and workers work on chunks

[akka-user] become(params) vs FSM

I'm considering using become(processing(params)) in some of my short-lived job actors, so that the params are available when the job completes, yet the job can be started separately from its creation. So I'm wondering about the overhead of become, and whether I should be considering the FSM stuff

Re: [akka-user] Re: Akka 5 Year Anniversary--Thank you guys

I'm sure this will be a long thread, but I must join in the congratulations. It's a wonderful piece of software and helpful community. You must be very proud. On Thu, Jul 10, 2014 at 10:00 AM, 09goral gora...@gmail.com wrote: Great job and thank you all for you work! W dniu czwartek, 10

Re: [akka-user] Questions about akka persistence and scalability

I just watched this ScalaDays talk which was pretty good http://www.parleys.com/play/53a7d2c3e4b0543940d9e53b/chapter0/about As I understand it, you either use ClusterSingleton or ClusterSharding (the latter if your aggregates are actors). The cluster sharding Activator template is a nice clear

Re: [akka-user] Routing to subset of children

there where children can subscribe to an interested channel on a bus. On Fri, Sep 5, 2014 at 11:44 PM, Richard Rodseth rrods...@gmail.com wrote: Suppose I have messages containing a channel id coming to a parent actor. There are many children, each of which is interested in one or more

Re: [akka-user] Manifest Event Sourcing Application's Performance

Not sure if this helps https://github.com/erikvanoosten/metrics-scala/blob/master/docs/Actors.md On Thu, Sep 11, 2014 at 3:48 PM, Ivan Topolnjak ivant...@gmail.com wrote: Prakhyat, for the record: Kamon does provide metrics on number of HTTP requests, average, min, max, counts per response

[akka-user] Per-request actor trait

I asked about this on spray-user, but thought I'd try here since this list rocks and it relates to Akka and an Activator template. I'm wondering how one would make this: https://github.com/NET-A-PORTER/spray-actor-per-request/blob/master/src/main/scala/com/netaporter/routing/PerRequest.scala

Re: [akka-user] Per-request actor trait

] } trait PerRequestCreator { this: Actor = def perRequest[Request](r: RequestContext,target: ActorRef, message: Request) = context.actorOf(Props(new WithActorRef(r, target, message))) } On Sat, Sep 13, 2014 at 5:47 PM, Richard Rodseth rrods...@gmail.com wrote: I asked about

[akka-user] Pipe list of futures independently

I'm still getting used to all the flavours of future composition. Fun stuff. Is there a better way than the following to pipe a list of futures to the sender (one message per future) ? val requests:List[Future[SomeResponse]] = ... val messages:List[Future[String]] = requests.map {

Re: [akka-user] Pipe list of futures independently

, Richard Rodseth (rrods...@gmail.com) wrote: I'm still getting used to all the flavours of future composition. Fun stuff. Is there a better way than the following to pipe a list of futures to the sender (one message per future) ? val requests:List[Future[SomeResponse]] = ... val messages:List

Re: [akka-user] Pipe list of futures independently

/ On 19 September 2014 at 20:46:50, Richard Rodseth (rrods...@gmail.com) wrote: I'm still getting used to all the flavours of future composition. Fun stuff. Is there a better way than the following to pipe a list of futures to the sender (one message per future) ? val requests:List[Future

[akka-user] Bridging spray router and service actors

Suppose I have an actor hierarchy like this: SprayAPIRoutingActor XYZServiceActor ..DbActor ..OtherActor1 ..OtherActor2 The DbActor wraps one or more blocking DAOs and has its own dispatcher to isolate the blocking. The router actor has access to the root service actor. I have implemented one

Re: [akka-user] Bridging spray router and service actors

Hi Endre Yes, the one I showed (onComplete()) *is* taking a future. The result of my ask is a Future[Long]. On Tue, Sep 30, 2014 at 3:58 AM, Akka Team akka.offic...@gmail.com wrote: Hi Richard, The route looks something like this: post { val result = (xyzService ?

Re: [akka-user] Routing to subset of children

://www.benhowell.net/examples/2014/04/23/scala_and_the_akka_event_bus/ Happy hakking! On Sat, Sep 6, 2014 at 7:18 PM, Richard Rodseth rrods...@gmail.com wrote: Thanks. For those, following along, this is helpful: http://www.kotancode.com/tag/event-bus/ On Sat, Sep 6, 2014 at 1:09 AM, Martynas

Re: [akka-user] Routing to subset of children

Excellent.. Thanks. On Wed, Oct 1, 2014 at 1:00 AM, Roland Kuhn goo...@rkuhn.info wrote: 1 okt 2014 kl. 03:45 skrev Richard Rodseth rrods...@gmail.com: Thanks, Konrad. I have a little test working, but I'm puzzled by one thing. If all I want to do is subscribe to individual channel ids

Re: [akka-user] Bridging spray router and service actors

, Akka Team akka.offic...@gmail.com wrote: Hi Richard, No, I mean the other complete() method that you call from the Success and Failure paths of the onComplete block. Why not just use complete(result.transform(...))? -Endre On Wed, Oct 1, 2014 at 2:01 AM, Richard Rodseth rrods...@gmail.com

Re: [akka-user] Bridging spray router and service actors

This looks interesting. Future.collect. Learn something new every day. http://www.superloopy.io/articles/2013/spray-routing-error-handling.html On Wed, Oct 1, 2014 at 11:00 AM, Richard Rodseth rrods...@gmail.com wrote: Thanks for clarifying. I was using the version of complete I showed

Re: [akka-user] Akka REST

There are a couple of Activator templates. It's common to use Spray, which is in the process of becoming Akka HTTP. https://typesafe.com/activator/template/activator-akka-spray On Tue, Oct 7, 2014 at 4:52 AM, naveen gayar navind...@gmail.com wrote: Hi Any example of Akka as a RESTful

Re: [akka-user] Akka REST

Once Spray is part of Akka as Akka HTTP I think they have a Java API planned, but I don't know when that is due to be released. There are lots of options for the web tier, including eg. Spring MVC and Play (which are full stack frameworks, but can be used to build REST APIs). On Thu, Oct 9, 2014

Re: [akka-user] Using Tell or Ask with Akka Persistence and REST

One thing I've done to preserve layering (and I'm new to this so take it with a grain of salt) is the following: Per-request request handler actor sends a command to a service actor (not per-request), including a requestor reference (self) in the message. Service actor is free to pass the

Re: [akka-user] Patterns to process futures in receive

I don't follow your snippet. Receive is a partial function from Any to Unit, so it doesn't return anything. def receive = { case Start = { val futureResult = someFuture someFuture pipeTo sender } } You don't need to add an ask- you can just pipe someFuture to self or the sender. The result will

Re: [akka-user] Patterns to process futures in receive

creating to much noise. I do not know it is possible, but I imagine that I could somehow tell the mailbox of the actor to proceed only when the future the actor had created is completed. Hopefully that makes more sense, Markus 2014-10-13 16:28 GMT+02:00 Richard Rodseth rrods...@gmail.com: I

Re: [akka-user] REST JAVA: Akka HTTP Vs Play Vs Spring

I think he's considering Play even for pure REST, because he can use it from Java, and Akka-HTTP is not ready. On Tue, Oct 14, 2014 at 7:40 AM, Daniel Armak danar...@gmail.com wrote: Spray / akka-http and Play address two different use cases. Spray/akka-http is an HTTP framework; as such it's

Re: [akka-user] Using Tell or Ask with Akka Persistence and REST

by their parent (which is very much by design). Regards, Roland 9 okt 2014 kl. 17:38 skrev Richard Rodseth rrod...@gmail.com: One thing I've done to preserve layering (and I'm new to this so take it with a grain of salt) is the following: Per-request request handler actor sends a command to a service

[akka-user] Akka Persistence Journal Access

I feel sure this must have been covered, but my searches are coming up blank. The benefits in terms of write-throughput are clear to me, but free auditing is often touted as a benefit of event sourcing, and one that can help sell the concept. So, are there supported APIs to get access to the

Re: [akka-user] Akka Persistence Journal Access

guess) new views API, which is covered in detail here: http://letitcrash.com/post/96687159512/akka-persistence-on-the-query-side-the-conclusion ​ On Sat, Oct 18, 2014 at 12:38 AM, Richard Rodseth rrods...@gmail.com wrote: I feel sure this must have been covered, but my searches are coming up

[akka-user] Resolve of unknown path to dead letters in Akka Persistence test

I have a simple test of Akka persistence with LevelDB. First app creates 1 aggregates, second app updates them, third app logs them (via a GetContent message). The good news is that the creation and updating seems pretty snappy. In the logging (GetContent) app, I get the following error (many

[akka-user] Event versioning revisited

I'm hoping to build a case for using Akka Persistence, and expect the event schema evolution to be a sticking point. People are quite used to their database migration scripts. I've seen the threads on this list, but I'm wondering what the current thinking is on the least painful option, and would

Re: [akka-user] Event versioning revisited

Thanks for the references, Patrik. I hope others will share their experiences. On Tue, Oct 21, 2014 at 4:57 AM, Patrik Nordwall patrik.nordw...@gmail.com wrote: Hi Richard, I'm also interested in what others are currently using. On Sun, Oct 19, 2014 at 3:35 AM, Richard Rodseth rrods

Re: [akka-user] Event versioning revisited

@gmail.com wrote: Hi Richard, I'm also interested in what others are currently using. On Sun, Oct 19, 2014 at 3:35 AM, Richard Rodseth rrod...@gmail.com wrote: I'm hoping to build a case for using Akka Persistence, and expect the event schema evolution to be a sticking point. People

Re: [akka-user] How to tell if a given persistent actor ever persisted something?

I think I would make the sessions persistent actors, children of a SessionManager that is not a persistent actor. The SessionManager can always see if a child exists. http://typesafe.com/activator/template/akka-persistence-event-sourcing

Re: [akka-user] How to tell if a given persistent actor ever persisted something?

persistent views by aggregating multiple persistent actors. Hope this helps. I'm new to this too. On Wed, Oct 22, 2014 at 8:14 AM, Richard Rodseth rrods...@gmail.com wrote: I think I would make the sessions persistent actors, children of a SessionManager that is not a persistent actor

Re: [akka-user] Event versioning revisited

and Heather Miller discusses it on Scalawags https://www.youtube.com/watch?v=uCpw9eBYbOw I also came across this ticket: https://github.com/scala/pickling/issues/39 On Tue, Oct 21, 2014 at 5:17 PM, Richard Rodseth rrods...@gmail.com wrote: Thanks for the input. I wonder if anyone has tried Scala

[akka-user] Actor State and State Changes

I had in mind that I would strive to have a single var in my actors, which was a reference to an immutable object. One issue I've run into that since the actors go through various states of initialization (using become), I find myself with bits of state which can't be initialized in the

[akka-user] Anticipating Akka Persistence

It must be frustrating for the Akka team to field questions when the solutions will be so much more elegant with Akka Persistence and Reactive Streams :) I have an aggregate which needs to respond to events by updating its own persistent state (using Slick) and firing a domain event. I believe

[akka-user] Testing per-request child creation

I have a parent actor which, on receipt of a certain message A, spawns a child actor, and sends it a Run message with no parameters. The child actor has constructor parameters derived from the contents of message A. What's the best way to test this? I don't think I can apply techniques like

Re: [akka-user] Testing per-request child creation

that the parent actor passed the correct set of results to the child constructor. On Tue, Nov 18, 2014 at 2:24 PM, √iktor Ҡlang viktor.kl...@gmail.com wrote: Hi Richard, what effects are you trying to test? On Tue, Nov 18, 2014 at 11:17 PM, Richard Rodseth rrods...@gmail.com wrote: I have a parent

Re: [akka-user] Testing per-request child creation

(but at a microlevel). On Tue, Nov 18, 2014 at 11:43 PM, Richard Rodseth rrods...@gmail.com wrote: The message A in the parent actor is computing a set of results. The per-request child will be saving some state from those results, and if successful, posting a domain event containing the results

Re: [akka-user] Testing per-request child creation

, Richard Rodseth rrods...@gmail.com wrote: Thanks for the input. I guess I can register a testprobe.ref as a subscriber to the event bus. I will still need to control the creation of the per-request child so that I can inject a mock storage interface that acks with success so that the posting

Re: [akka-user] Testing per-request child creation

, Nov 19, 2014 at 3:48 AM, √iktor Ҡlang viktor.kl...@gmail.com wrote: I'm not sure I follow. Test for what message and what effect? On Wed, Nov 19, 2014 at 1:05 AM, Richard Rodseth rrods...@gmail.com wrote: This does rather beg the question of what the integration boundary is, and also

Re: [akka-user] Testing per-request child creation

internal state? On Wed, Nov 19, 2014 at 4:53 PM, Richard Rodseth rrods...@gmail.com wrote: Sorry. The parent actor P gets a message containing measurement data. It calculates a sequence of notifications about that data, which it passes to the per-request child after become()ing saving

Re: [akka-user] Testing per-request child creation

I already have non-actor classes for the evaluation of notifications and the internal actor state, but I do think it's legitimate to want to test the actor behaviour. I mentioned the GetInfo message, because Viktor was inspiring me to think of this an an integration test and asked if I could check

Re: [akka-user] Testing per-request child creation

, Richard Rodseth rrods...@gmail.com wrote: I can use underlyingActor, but perhaps that doesn't qualify as from the outside. I might have a GetInfo message I could use (that exists to support a REST API). On Wed, Nov 19, 2014 at 7:59 AM, √iktor Ҡlang viktor.kl...@gmail.com wrote: Can you

Re: [akka-user] Any limits on using Akka futures to make *ANY* blocking call to be asynchronous?

Have you seen the Blocking Needs Careful Management section here? http://doc.akka.io/docs/akka/snapshot/general/actor-systems.html On Fri, Dec 5, 2014 at 12:57 PM, David davidlu...@gmail.com wrote: Hi, Futures seem magical. It looks like you can hand off *ANY* process to a thread pool,

[akka-user] Drain mailbox on shutdown

I've read some of the posts on shutdown patterns, reapers, graceful shutdown and the like, but am still unclear on the best strategy for my situation. The system is generating records to be written to a database. A single actor is doing this writing, in response to messages. When the system is

Re: [akka-user] Drain mailbox on shutdown

, 2014 at 1:26 AM, Richard Rodseth rrods...@gmail.com wrote: I've read some of the posts on shutdown patterns, reapers, graceful shutdown and the like, but am still unclear on the best strategy for my situation. The system is generating records to be written to a database. A single actor

[akka-user] Domain Events, Aggregate Persistence Events and cross-aggregate consistency

I should probably go back and read some of the threads about Akka persistence and CQRS/ES. The system I'm working on has actors (let's call them Monitors) that monitor event data and generate Alerts. Both Monitors and Alerts are entities with persistent state. In DDD terms, I think of them both

Re: [akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

Hi Vaughn Thanks so much for replying. I have your excellent book and the Blue Book, but obviously I'm still a bit unclear on some things. So you are giving unique identity to Domain Events? That sounds less like Event Sourcing already. While that can be done (and my book discusses it), it

Re: [akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

It's not obvious to me that Alerts are part of the Monitor aggregate, but perhaps they are, with the in-memory model containing only the last alert, and a Read Model Projection, to use the term in Appendix A, to allow querying of alerts. On Thu, Dec 18, 2014 at 1:38 PM, Vaughn Vernon

Re: [akka-user] Akka Roadmap Update

than deployment machines, in which scenario does this question come up? Regards, Roland 18 dec 2014 kl. 19:09 skrev Richard Rodseth rrods...@gmail.com: Hi Roland In a mixed Java/Scala project that does not use Java APIs to Akka, Play etc, would the Java code need to be compiled

Re: [akka-user] Akka Roadmap Update

, Roland Kuhn goo...@rkuhn.info wrote: 19 dec 2014 kl. 20:35 skrev Roland Kuhn goo...@rkuhn.info: 19 dec 2014 kl. 20:09 skrev Richard Rodseth rrods...@gmail.com: Hi Roland I'm relaying (not very well) questions from colleagues. We don't deploy VM’s or docker containers. Our first step would

Re: [akka-user] Akka Roadmap Update

I'm sure you're right. Sounds like upgrading both JRE and JDK throughout will be a prerequisite for using Akka 2.4. On Fri, Dec 19, 2014 at 1:53 PM, Roland Kuhn goo...@rkuhn.info wrote: 19 dec 2014 kl. 22:38 skrev Richard Rodseth rrods...@gmail.com: Sorry, you lost me there. Java 6

Re: [akka-user] Re: Event versioning revisited

I see Scala pickling has a stable release http://notes.implicit.ly/post/110275857699/pickling-0-10-0 If anyone has any updates on its viability for event versioning, please post. On Thu, Oct 23, 2014 at 1:16 PM, Christian Douven chdou...@gmail.com wrote: We are using MessagePack as our binary

Re: [akka-user] Again about tell don't ask and use Actor tell instead future

Hi Vladimir I have had good luck with using per-request actors as in the Net-a-porter activator template, and a replyTo:ActorRef in the messages sent to my DbActor (which still talks to a DAO) Some more detail in this thread

Re: [akka-user] Re: Akka CQRS / Cluster Sharding - Change management of Events and other questions

My favourite topic https://groups.google.com/forum/#!topic/akka-user/mNVxRPRUDv0 Jay Kreps recently strongly endorsed Avro for use with Kafka. http://t.co/l9uTFmb6OS On Mon, Apr 13, 2015 at 10:54 AM, Greg Young gregoryyou...@gmail.com wrote: For 1 use weak serialization (say json) On

Re: [akka-user] Akka HTTP TLS support ETA?

Roland tweeted yesterday: Yesterday the #jaxcon https://twitter.com/hashtag/jaxcon?src=hash award, today merged HTTP client (@sirthias https://twitter.com/sirthias) and WebSockets (@virtualvoid https://twitter.com/virtualvoid) and TLS support—can tomorrow be even better? On Fri, Apr 24, 2015

[akka-user] Activator: akka-stream-scala template compilation error

You're probably aware of this already: [error] /Users/rrodseth/dev/samples/akka-stream-scala/src/main/scala/sample/stream/GroupLogFile.scala:34: too many arguments for method mapAsync: (parallelism: Int)(f: ((String, akka.stream.scaladsl.Source[String,Unit])) =

Re: [akka-user] Re: Akka Persistence on the Query Side: The Conclusion

Hi Olger Could you please elaborate a bit on your appoach? I'm not sure I follow. Thanks. On Fri, May 8, 2015 at 4:17 AM, Olger Warnier ol...@spectare.nl wrote: Hi Alejandro, You have a number of options - when you have a single persistence Id, write a view for that - when you want to

Re: [akka-user] Re: Akka Persistence on the Query Side: The Conclusion

PM, Richard Rodseth rrods...@gmail.com wrote: Hi Olger Could you please elaborate a bit on your appoach? I'm not sure I follow. Thanks. On Fri, May 8, 2015 at 4:17 AM, Olger Warnier ol...@spectare.nl wrote: Hi Alejandro, You have a number of options - when you have a single

Re: [akka-user] Re: The best ways to resolve future inside an actor?

Have you looked at the pipeTo pattern and the Stash trait? I'm not sure why a combination of pipeTo and become() with Stash wouldn't work. On Thu, May 14, 2015 at 4:33 AM, Andrew Gaydenko andrew.gayde...@gmail.com wrote: It's funny just now I have met the same situation! :) More strictly, my

Re: [akka-user] Per-request vs Work Pulling vs Dispatcher tuning

give a different dispatchers to the Futures)? -Endre On Fri, Apr 3, 2015 at 9:36 PM, Richard Rodseth rrods...@gmail.com wrote: At startup our application reads a bunch of rows d of type D of a table, and for each sets in motion a bunch of Spray client calls and other database calls

Re: [akka-user] NewRelic Integration for Akka Application

Have you looked at Kamon? On Tue, Apr 7, 2015 at 1:49 PM, K.M. Fazle Azim Babu azim.b...@gmail.com wrote: Hi, I have application written using Akka library, and I want to use New Relic to monitor it. I tried to instrument the akka application using Newrelic's custom java transaction

Re: [akka-user] Integrating different Bounded Contexts

You don't want more than one ActorSystem per process. If each BC is a separate process (a la microservices) then having something like Kafka to durably message between them would be great. Within an ActorSystem, you can use the Akka EventBus to (non-durably) message between root-level actors that

Re: [akka-user] Re: Integrating different Bounded Contexts

So each BC is an Akka Cluster, and you are relying on remote Akka (remote) messages to propagate changes from one BC to another? That sounds risky. Implementing DDD has a section (p303) called Spreading the news to Remote Bounded Contexts On Fri, Jun 5, 2015 at 11:18 AM, Guido Medina

Re: [akka-user] Re: Integrating different Bounded Contexts

Oh, I misunderstood. Thanks for clarifying. I'll be interested in other reactions. My impression (perhaps incorrect) is that a small subset of Akka users are using Akka Cluster. On Fri, Jun 5, 2015 at 3:24 PM, Guido Medina oxyg...@gmail.com wrote: No, I have a single cluster, each micro-service

Re: [akka-user] [2.3.11] Is akka.persistence production ready?

Amir, you asked about alternatives. It seems Martin Krasser is no longer involved with Akka Persistence and has his own project Eventuate. I don't have any experience with it (or Akka Persistence for that matter), but here's a recent blog post:

Re: [akka-user] [2.3.11] Is akka.persistence production ready?

once we have Akka Streams (which are nearing 1.0 now) Eventuate is a nice project, and as Martin describes in the blog post it chooses a different trade off (AP) than Persistence (CP). -- Konrad On Fri, May 29, 2015 at 4:09 PM, Richard Rodseth rrods...@gmail.com wrote: Amir, you asked about

[akka-user] Stamina

No, not referring to the effort required to keep up with the Akka team :) I just came across this: https://github.com/scalapenos/stamina and wondered if anyone had any thoughts about it. I'm itching to pitch Akka persistence, but would like the read side and serialization to be well-baked. --

Re: [akka-user] Re: Dealing with exceptions with pipeTo

I sometimes call recover on the returned Future to generate a message of my own, before doing the pipeTo. On Wed, Aug 5, 2015 at 6:30 AM, Johan Andrén johan.and...@typesafe.com wrote: pipeTo will wrap failures in an akka.actor.Status.Failure and send that to the actor that you direct the

Re: [akka-user] ShardRegion vs EventBus

with sendOneMessageToEachGroup and a custom routing logic? Thanks for any thoughts on this use case. On Fri, Jul 10, 2015 at 9:11 AM, Richard Rodseth rrods...@gmail.com wrote: But I'll take a look, thanks. Not sure if one topic per channel is feasible. On Fri, Jul 10, 2015 at 9:04 AM, Richard Rodseth

Re: [akka-user] ANNOUNCE: Akka Streams HTTP 1.0

Great news. Once the new modules are merged into 2.4, will the only changes to the 2.3 artifacts be bug fixes? On Wed, Jul 15, 2015 at 5:40 AM, Konrad Malawski ktos...@gmail.com wrote: Dear hakkers, we—the Akka committers—are very pleased to announce the final release of Akka Streams HTTP

Re: [akka-user] Re: Spray 1.3.3 and Aka 2.4

Good to know. My apps seem to be running too (at least on my laptop). One of the services was getting an out of memory error with debug logging turned on, but I think it was a function of all the other stuff I had running at the same time. I'll probably hold off until I can do more careful

Re: [akka-user] Re: Akka and Fibers: Any Plans?

> > > What's in the case of Akka the way to prevent threads (that is actors) > from blocking when doing blocking IO (querying databases, doing REST calls, > reading from files, etc.)? Go through NIO or is there some stuff provided > for this? > > Thanks for any answers. >

[akka-user] Spray 1.3.3 and Aka 2.4

Is this possible? I've learned that migration from Spray to Akka HTTP is not always trivial, and that the performance is not yet there, but would like to benefit from the other goodies in 2.4. Thanks. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ:

Re: [akka-user] Re: code that will block for some time, part of an actor or should I wrap it inside a Feature?

Also see http://doc.akka.io/docs/akka/snapshot/general/actor-systems.html#Blocking_Needs_Careful_Management On Tue, Nov 10, 2015 at 2:04 PM, Guido Medina wrote: > I have actors such like *AccountProcessor* and *AccountPersistor*, > AccountPersistor is a child of

[akka-user] Akka/Kafka

Apologies if this is a naïve question. Kafka seems like great technology and a great companion to Akka. It has a dependency on Zookeeper, and my understanding is that's just for the watermarks. I'm not sure if this dependency on ZK is a bad thing, but I've certainly seen criticism of ZK and

Re: [akka-user] Akka/Kafka

derstand all the ramifications. > > Regards, > > Roland > > 17 nov 2015 kl. 02:02 skrev Richard Rodseth <rrods...@gmail.com>: > > Apologies if this is a naïve question. > Kafka seems like great technology and a great companion to Akka. > It has a dependency on Zookeepe

Re: [akka-user] ShardRegion vs EventBus

But I'll take a look, thanks. Not sure if one topic per channel is feasible. On Fri, Jul 10, 2015 at 9:04 AM, Richard Rodseth rrods...@gmail.com wrote: Nope. I imagined it to be for broadcasting, rather than having something analagous to LookupClassification. On Fri, Jul 10, 2015 at 12:16 AM

[akka-user] ShardRegion vs EventBus

We're not using Akka Cluster yet, but I have an entity actor type that is ripe for sharding. But there's a complication. The numerous entities are receiving event data for various channels, and rather than receiving messages directly from the supervisor, the supervisor publishes them to an

Re: [akka-user] akka http actor per request

I ended up breaking down and doing an ask (to a request handler actor) in the route definition. The request handler creates a per-request actor with the requestor as a constructor parameter, and from then on I use no more asks, but pass replyTo in tell messages. So there is not a chain of asks,

Re: [akka-user] Can Akka actors deadlock?

Have you looked at Future.sequence? It turns a List[Future[A]] into a Future[List[A]]. Then you can pipe that result to the same actor or another, or add a complete handler as you have done. On Wed, Aug 26, 2015 at 11:17 AM, kraythe kray...@gmail.com wrote: I am using play framework with a mix

  1   2   3   >