Re: [akka-user] Cancel Actor job

Maybe this distributed workers guide could be good inspiration: https://developer.lightbend.com/guides/akka-distributed-workers-scala/ -- Johan Akka Team On Fri, Feb 2, 2018 at 3:10 AM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > Have a look at "cluster sharding”, it’s smar

Re: [akka-user] Re: ANNOUNCE: Akka Multi-DC Persistence

Hi Patrik, Thanks for your reply! I think I'll go with implementing the dynamic solution for my project: we're fine with causal eventual consistency, and we think being available during intra-DC netsplits will be beneficial. Another reason I didn't mention is that we need a particular schema fo

[akka-user] Re: Proper way to handle the Entity Stream Truncation Exception

Anyone got any updates on this issue. I am having similar problem where akka http client respond with a Success(OK) and then stream gets truncated while entity.dataBytes.runFold(ByteString(""))(_ ++ _). The size of the data received is ~20Mb. Thanks Vimal. On Wednesday, June 29, 2016 at 12:33:

Re: [akka-user] Akka typed - first impressions

I have published a snapshot of latest Akka Typed progress if you would like to try it out. Version 2.5-20180202-18 in repo https://repo.akka.io/snapshots/ Latest documentation: https://doc.akka.io/docs/akka/snapshot/typed/index.html Cheers, Patrik On Tue, Jan 30, 2018 at 10:27 AM, Tal

[akka-user] Akka, Akka Typed and dead code elimination

Hi everyone, I’ve got a requirement to run services on machines with limited resources, memory in particular, but also disk (disk == memory for my use case!) In addition, I wish to reduce the attack surface area of a service by eliminating code that isn’t used. I’d therefore like to take a uni

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Christopher, I’ve worked in the past on an Scala on Android project, so have had the “pleasure” of battling proguard for similar reasons. In general I guess the “core stuff” needs to be kept, which would mostly be the akka.actor and dungeon things. AFAIR proguard is ale to understand references

Re: [akka-user] Akka, Akka Typed and dead code elimination

Thanks for the reply Konrad. Although my use-case is somewhat forced by working with constrained device memory and enterprise security, I think that there’s a broader concern. My understanding is that the JVM is embracing ahead of time compilation and the potential for dead code elimination dur

Re: [akka-user] Akka, Akka Typed and dead code elimination

Really Christopher… we’re not heavy on reflection, check other libraries in the Java ecosystem ;-) The single reflection things we have is classOf style actor creation, and initial startup things, that’s it. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Christopher, could you elaborate on how exactly Akka Typed is expected to help with your use-case? The only difference I can see is that the new (and currently removed) implementation contained fewer extension points, but that is unrelated to whether ActorRef has a type parameter or not. Re

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Roland, > On 3 Feb 2018, at 5:16 pm, Roland Kuhn wrote: > > could you elaborate on how exactly Akka Typed is expected to help with your > use-case? The only difference I can see is that the new (and currently > removed) implementation contained fewer extension points, but that is > unrelat

Re: [akka-user] Akka, Akka Typed and dead code elimination

Sent from my iPhone > On 3. Feb 2018, at 07:25, Christopher Hunt wrote: > > Hi Roland, > >> On 3 Feb 2018, at 5:16 pm, Roland Kuhn wrote: >> >> could you elaborate on how exactly Akka Typed is expected to help with your >> use-case? The only difference I can see is that the new (and curren

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Roland, > On 3 Feb 2018, at 5:56 pm, Roland Kuhn wrote: > > I agree on the tendency. In the case of Akka there are two reasons for using > reflection and neither of them is caused by a lack of static types: > extensibility and remote marshaling. A new implementation could remove > configur