I am writing some worker actors that perform operations with external
resources and I wonder whether I should strive to make them short-living or
reuse them. Consider two main scenarios:
1. Worker actor is doing IO operation that isn't limited with constraints
like connection pooling, throttlin
ak at the end.
>
> On Wednesday, December 30, 2015 at 11:35:33 AM UTC, Vagif Abilov wrote:
>>
>> Hello,
>>
>> We want to use Akka to implement a scenario when messages are fetched
>> from a message queue (RabbitMQ) and then processed by a chain of actors.
>>
Hello,
We want to use Akka to implement a scenario when messages are fetched from
a message queue (RabbitMQ) and then processed by a chain of actors. The
queue is durable and messages must not be lost. So we need to send an
acknowledgement (BasicAck in RabbitMQ) back to the queue in order to
f
ing Akka, sure; but why? They're hard
> problems. Just use RabbitMQ. It's battle tested and it's one less custom
> thing everyone on your team will need to learn.
>
> Tim
>
> On Dec 2, 2015, at 04:05, Vagif Abilov >
> wrote:
>
> Thanks, Tim. No, I hav
ibe in a way that keeps the complexity out of your
> codebase. It's well tested and is being used in several production
> environments (of which I'm aware).
>
>
>
> On Tuesday, December 1, 2015 at 1:10:37 AM UTC-7, Vagif Abilov wrote:
>>
>> Hi,
>>
&g
Hi,
I am quite new to Akka and am currently investigating if it's a good idea
to replace some of our logic built around AMPQ (RabbitMQ) with Akka and
actor model. Here's one of our scenarios:
1. Receive a message from RabbitMQ.
2.1-2.n Perform several operations, some of them in a transaction s
