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. Regards, Patrik On Tue, Aug 18, 2015 at 7:09 PM, Dan Di Spaltro <dan.dispal...@gmail.com> wrote: > 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 other things about the session and >> maintaining its state in a single actor. Now I am looking to add fault >> tolerance to that actor for when I need to either rebuild my Index for >> slicing and dicing, or I need to answer questions directly. >> >> Say I also am familiar operationally with Kafka, I was thinking in theory >> they'd fit well together however, one big design issue: It creates a topic >> per persistent actor, which is bad in my use-case. So I was thinking >> similar to how the ClusterSharding works, you have a shard extractor and Id >> extractor. I almost want the same thing, one actor per shard that holds >> the permanent events then spawns other actors that hold their session state >> but aren't themselves persistent. Then I was thinking someone might have >> thought of a better way to get around this or to think about this problem >> differently. I've looked through [1][2][3] to see if there's a pattern I'm >> missing, but I don't think I still fully grok how to design around this >> problem. >> >> Any ideas, comments? >> >> -Dan >> >> [1] https://github.com/boldradius/akka-dddd-template >> [2] https://github.com/jgordijn/cqrs_template#master >> [3] https://github.com/actorapp/actor-platform >> > -- > >>>>>>>>>> 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 because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to akka-user+unsubscr...@googlegroups.com. > To post to this group, send email to akka-user@googlegroups.com. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> 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 because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
