Hi All :) I am new here and new to designing distributed systems. My goal is to build a product that connects to different web services, gathers data and depending on this new infromation makes other calls to these services. You can imagine it as trading platform but not high frequency trading where every second matters. I have been thinking about how this system should be designed, how to distribute work so monitoring and supervision would be easiest. I will post my architecture design soon but the main reason I am here is how to build a decision point in my system. I have been thinking that I need one place where all information is gathered, so called brain of the system, that has all knowledge about current system state. This one node would make decision which of available services should post a trade. My main concern is that it caneasily become single point of failure and lead to taking down all system.
Has any of you experience with such problems? What can you suggest? Thank you :) Mateusz -- >>>>>>>>>> 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.
