Yeah it definitely makes it more complicated, I moved away from now and
will figure something out later, wanted to see if the community had a
solution for this at the granularity I was looking for.
Either way, thanks for the response!
-Dan
On Monday, August 31, 2015 at 6:37:45 AM UTC-7, Patrik
Hi Dan,
If Kafka can't handle many topics then it might not be suitable to use
Kafka as journal for that type of application.
I think your idea with looping the persistent events through a parent
PersistentActor could work, but you need to implement the delegation, error
handling and recovery.
R
Hi Dan,
If Kafka can't handle many topics then it might not be suitable to use
Kafka as journal for that type of application.
I think your idea with looping the persistent events through a parent
PersistentActor could work, but you need to implement the delegation, error
handling and recovery.
R
Any ideas here? I was curious how others approached the
high-number-of-journals in akka/kafka land.
Thanks!
On Wednesday, August 12, 2015 at 5:06:43 PM UTC-7, Dan Di Spaltro wrote:
>
> So imagine I am building a session tracking system. Where I am feeding
> the session header, events, and othe
