Hello all, I am getting started on my first AKKA project and need some help. Found a post related to database access , but could not conclude from that.
I have an use case where I am trying to use AKKA to add resiliency in our code base, where I need to access/update the database. Assuming that I would create a pool of worker actors per database to scale, each of these would need to share connection pool and also circuit breaker [will have one per DB] . Reading the AKKA docs, my understanding is that actors dont share state. Given this is it better to use actors (which will need to access 2 common resources) or futures. 1. is it ok if Master DB actor for that DB creates a connection pool, circuit breaker and passes these 2 during each DB execution in worker actor. 2. Assuming no sharing state and only 1 actor per DB, then the approach would be to use Futures to process concurrent DB requests. 3. Is there any other approach ? Kindly provide some thoughts as its slightly unclear as of now. Thanks -- >>>>>>>>>> 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.
