[akka-user] Re: is it possible to assure every message to be processed

Yes... the default in akka is at-most-once due to the performance hit that is inevitable with guaranteed delivery. To guarantee delivery you must have message persistence, but there are a number of ways to achieve this. We built a financial system with akka and used a few different tools for gu

[akka-user] Re: Patterns for ensuring perpetual existence of sharded actors

I agree - if you control the client then a client-side heartbeat is a good approach. I haven't had quite that requirement for the actors to always be instantiated but I have had a couple semi-related requirements. In one case we basically did the same heartbeat on the server side (we had a poo

[akka-user] Re: Implementing ACID style processing using Akka?

ugh double-post... I left out the Pat Helland link https://www.youtube.com/watch?v=EWSRbRUH7pg On Thursday, May 12, 2016 at 11:41:24 PM UTC-4, kraythe wrote: > > I have a system that is a traditional DB centric app for the most part. > However the data is loaded in a memcache for speed and ease

[akka-user] Re: Implementing ACID style processing using Akka?

Maybe a little late to the conversation but thought I'd add my 2 cents. I'm in the middle of implementing a financial system on top of Cassandra (not my choice but in retrospect it's forced me into decisions that I think are better than if I had relied on an ACID-compliant database). First off

[akka-user] Re: Cassandra Journal < v2.0.3?

> of Cassandra v 1.2.x, hoever the plugin available works for version 2.0.3 > or higher. Came across your post, did you happen to implement/tweak the > journal for older version of Cassandra ? If yes would share it with us or > let us know what were the tweaks required. Thanks for

Re: [akka-user] how to learn AKKA?

+1 for the activator... it's got lots of example apps each with great tutorials explaining the code (which you can see side-by-side in the browser) and makes it simple to tweak/execute right there to get a feel for things. I'd start with a run through the docs to get up to speed with the concep

Re: [akka-user] Re: Pulling Pattern vs Durable Mailboxes

Very helpful, thanks Martin. -- >> 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/group/akka-user --- You received this message be

[akka-user] Re: Pulling Pattern vs Durable Mailboxes

Apologies for the double-post. The below thread re: throughput and performance benchmarks seems relevant... including for my future self: https://groups.google.com/d/msg/akka-user/7GE495Ks-5c/YntYlSCd4ysJ -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>>

Re: [akka-user] Re: Pulling Pattern vs Durable Mailboxes

On Wednesday, May 7, 2014 12:57:23 AM UTC-4, Martin Krasser wrote: > > > Please not that the primary use case for persistent channels is to deal > with slow and/or temporarily available consumers/destinations. It is not > optimized for high throughput (yet). More detailed, a persistent channel >

Re: [akka-user] Re: Pulling Pattern vs Durable Mailboxes

On Tuesday, May 6, 2014 2:06:16 AM UTC-4, Martin Krasser wrote: You may be interested in this pull requestthat enables reading from akka-persistence journals via reactive-stream >> producers. > > Yea, actually that looks much like what I had in mind.

[akka-user] Re: Pulling Pattern vs Durable Mailboxes

Our design is still a bit young, but we're going with a work pulling pattern right now... which is something that has worked well for me in the past (this is my first Akka impl though). In terms of the overall approach of using a queue/datastore effectively as a replacement for a mailbox (or im

[akka-user] Re: Pulling Pattern vs Durable Mailboxes

> > This got me thinking about a possible alternative to doing this pulling > pattern which is to do pushing but with durable mailboxes. An example I was > thinking of was implementing a mailbox that used RabbitMQ (other data > stores like Redis, MongoDB, Kafka, etc would also work here) and th

[akka-user] Cassandra Journal < v2.0.3?

Has anyone implemented an akka persistence journal for older versions of Cassandra? I see the current journal is dependent on C* v2.0.3 or higher (https://github.com/krasserm/akka-persistence-cassandra) but my app is currently on 1.1.9 and we are only actively planning to upgrade to v1.2 (just