Hi Viktor, Although this thread's activities seem to be gone for a while, I allow myself to post a question/suggestion here.
My use case: I'm looking for a pub-sub mechanism that will allow distributed data updates on clients that belong to the same organization. There might be hundreds or more organizations (hopefully) each having a one to about five people working simultaneously. A change of one should trigger an update on all members working for the same company. This would mean I have a large number of channels (or topics) each having only few (say 1-50) subscribers. Still, there may be significant traffic and the mediator might be a bottleneck here. Typically, one starts out with a small scale of an application, but would like to be prepared for its growth. Knowing how it can grow will allow you to avoid getting tied. In the last section of: http://doc.akka.io/docs/akka/2.3.6/contrib/distributed-pub-sub.html is written: "...it can be good to know that it is possible to start the mediator actor as an ordinary actor and you can have several different mediators at the same time to be able to divide a large number of actors/topics to different mediators. For example you might want to use different cluster roles for different mediators." Maybe it is obvious for someone familiar with akka how this can be achieved, but for me - just evaluating its use - a sample for multiple mediators might be very helpful. Cheers, R. On Tuesday, November 5, 2013 2:28:45 PM UTC+1, √ wrote: > > > > > On Tue, Nov 5, 2013 at 2:16 PM, Peter Wolf <opu...@gmail.com <javascript:> > > wrote: > >> Excellent. I get it. Thanks Bjorn >> >> You might want to add a paragraph explaining this to your Tutorial >> >> Remote Actors is the coolest part of your technology. However there >> seems to be several different mechanisms for hooking them up (e.g. >> Microkernel, config file, DistributedPubSubExtension). It is hard for a >> learner to separate them and get going. Your Activator tutorials are a >> huge help. >> > > The Microkernel is how you deploy an Akka application, this is unrelated > to remoting. > The configuration is thoroughly explained in the documentation: > http://doc.akka.io/docs/akka/2.2.3/contrib/distributed-pub-sub.html + > http://doc.akka.io/docs/akka/2.2.3/general/configuration.html > The DistributedPubSubExtension does have documentation and I guess if you > haven't read the cluster documentation before you read the DPSE docs then > you're starting in a suboptimal order. > > Do you have any concrete advise as to how the documentation would be > easier to consume we're all ears! > > Cheers, > √ > > >> >> Thanks again >> P >> >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> 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 akka-user+...@googlegroups.com <javascript:>. >> To post to this group, send email to akka...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Cheers, > √ > > * Viktor Klang* > *Director of Engineering* > Typesafe <http://www.typesafe.com/> > > Twitter: @viktorklang > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
