FYI... looks like I accidentally replied to Soumya privately the last time, so I'm pasting the conversation back here for general reference...
On Sat, Aug 2, 2014 at 3:40 PM, lakshmi wrote: > Soumya, > > Thanks for your prompt response! I was trying to reply to your post, but I > guess I used the private reply by mistake :) > > Should I pull this back into the main conversation? > Your wish. I think you can be more eyes and better advice as well. > We want to subscribe to changes in 2 databases, so yes we will use > channels. We also plan to persist updates to hashes in one of the dbs. We > already have an internal Jedis common lib which we might try reusing for > this. If blocking becomes an issue and rediscala integrates well with Java, > we will give it a shot. > Have you ever extends an Scala actor in Java ? If yes then you should be able to use redisscala. I think yesterday someone release another Scala library for Redis. You may also want to evaluate that. > > In terms of the actors, does the design seem okay to you? If you see our > diagrams attached to the ticket (btw our design has since been updated to > use only 2 dbs - Topic and Status), we want to separate the concerns of > listening to the redis db changes versus persisting changes from other > actors. To make it transparent to external actors, we put a SyncActor in > front of the Listener and Persister. For example, in our use case the Topic > db is a listen-only db. And the Status db is a persist and listen db. We > plan to have interested actors listen to messages published by the > SyncActors to take action on them as necessary. > > I've not seen all the details of your design. My rule of thumb (and remember I'm not an Akka expert) is to put as little logic in one actor as possible. Just distribute the logic across as many actors as you can. > Would you happen to have any thoughts on this? > > Thanks! > > lakshmi > > > On Sat, Aug 2, 2014 at 10:50 AM, Soumya Simanta wrote: > >> Ive never tried using Scala drivers from Java because all my code is in >> Scala. However, I do believe that it should be possible with some extra >> effort. Do you plan to use redis channels or only the access other >> structures (SET, HASH, ZSET etc) in Redis. I think the only tricky part of >> using it in Java would be the channel which in theory should be doable as >> well. >> >> Good and please let me know if you have more questions. >> >> -Soumya >> >> >> >> On Sat, Aug 2, 2014 at 1:42 PM, lakshmi wrote: >> >>> Soumya, >>> >>> Thanks for the info on Rediscala. The automatic connectivity feature >>> seems very useful! We would love to be able to use a non-blocking driver, >>> but want it to be compatible with Java as we don't see a move to Scala in >>> the immediate future. Will Rediscala be compatible with Java applications? >>> Also do you know anything about Redisson which is for distributed systems? >>> >>> Appreciate your input. >>> >>> Thanks, >>> lakshmi >>> >> -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
