I'll echo the answer Justin provided. I normally taken existing DB access code and wrapped it in an Actor with Futures without issues. Was there any specific use case outside of your typical DB interactions (such as trying to take advantage of Event Sourcing)?
On Friday, May 13, 2016 at 10:13:57 PM UTC-4, kraythe wrote: > > Greetings, > > I have a legacy app with an existing RDBMS and I would like to convert it > to be an actor system. I have been researching this and came across Akka > persistence but the documentation is thin on how to wire this into legacy > backends. Furthermore, because of the high volume of legacy analytics code > outside my influence, rewriting the system to not use that database, or > making radical schema changes, would be politically impossible so that > rules out going to something like a journaled persistence mechanism for > Akka persistence. That leaves me in a bit of a quandary. So I was > interested in people who have had success integrating an actor system with > RDBMS and how they went about the process. Any help would be useful. > > -- Robert > -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
