I am currently evaluating Scala Akka to build out a real-time (soft) trading system for my employer. This will be my first attempt at building a system with concurrent processes and using Akka. I have a good understanding now of how to use Akka to design and implement the system. However I am unsure about the following:
What are the proven best strategies to have in place in order to debug an Akka based concurrent system? Say I have a complex messaging environment where my actors are firing many many messages based on deterministic and random external stimuli and a glitch occurs, what techniques has the community found to be helpful in pinpointing the exact problem quickly. I ask this because traditional non Akka based multithreaded systems are notoriously difficult to debug. I would like to know has Akka helped in anyway to ease this type of debugging task in any way. I would like to promote Akka in m workplace but if I can't prove that debugging an Akka system is easier than traditional java based multithreaded systems then I'm going to find some resistance to get it adopted. -- >>>>>>>>>> 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.
