Hi, I will be able to tell you more about experiences with Spread in the coming months.
Our site has recently been moving to upgrade our load balancing and high availability capabilities using mod_backhand for Apache-based load balancing and Wackamole/Spread for high availability. These tools are created by the Center for Networking and Distributed Systems at Johns Hopkins University. http://www.backhand.org/ http://www.backhand.org/wackamole/ http://www.spread.org/ http://www.cnds.jhu.edu/ We will not be using any proprietary front-end load balancers at all. And the peer-oriented Wackamole solution allows for all of the servers to be in play rather than having some systems serve as quiet "backup" systems, simply waiting for their primaries to fail. (as described by the Linux Virtual Server project, http://www.linuxvirtualserver.org/HighAvailability.html) I also note that this approach allows for Perl Application Servers based on Apache/mod_perl (as discussed at length in recent threads) to automatically have load balancing and high availability properties (when configured, of course). The fact that our high availability and load-balancing architecture is evolving on top of this suite of tools indicates that Spread (in the form of Spread::Queue for Perl, http://search.cpan.org/author/JMAY/Spread-Queue/) holds great promise as a reliable network messaging system. If anyone else has actual experience with any of these tools, I welcome your input. Stephen At 08:42 AM 11/29/2002 +0100, Bas A.Schulte wrote: >Hi, > >On Wednesday, November 27, 2002, at 07:42 AM, Perrin Harkins wrote: > >> I think message beans do sound attractive in this situation, and there >> is some infrastructure code to write here on the Perl side (putting >> messages in the database, reading them back out of it, triggering the >> appropriate handling code, and maybe throttling if you can find a way >> to make it generic enough). It wouldn't be hard to make some modules >> that do what I described with cron, an RDBMS, and mod_perl, and that >> might be a good addition to CPAN. Or maybe a generalization of Jason's >> Spread::Queue is in order. People do seem to bring up messaging/queues >> a lot on this list. > >I would be interested in people's experience using Spread (from perl). >What are you doing with it from a functional point of view? How well >does it work? Likes/dislikes? > >I'm mostly interested in it being used for one-to-one or one-to-many >publishing of reliable/ordered messages. > >One other thing: from reading the docs it appears Spread itself doesn't >do persistent storage of messages (i.e. a receiver is unavailable), Did >you solve that? If so, how? > >Thanks for any feedback, > >Bas. > > >
