I don't know of any such local store and forward for PHP, but I think the concept is good. We have experienced issues where an ActiveMQ broker freezes and blocks all PHP clients, which in turn can tie up all currency in the website. You might do something as simple as staging message to the local filesystem and having a daemon forward them on to AMQ.
On a philosophical note, there seems to be an irony in having your site go down while blocking on something that's supposed to be asynchronous... On Wed, May 13, 2009 at 9:20 AM, zmiq2 <[email protected]> wrote: > > I'm a newbie in activemq, and haven't found much info about setting the > correct architecture for a high performance php - activemq cluster. > > My planned architecture is: > - activemq in server SQ > - php in servers S1, S2 > > But i'm afraid of every call to a php script, have the php open a network > connection to SQ, and then send the message to be handled. My idea would be > to have each php server, S1 and S2, have a little queue relay where php > scripts connect to its local relay, and it's the relay who, with a > permanent > link to SQ, manages the message transmission. > > How does this architecture sound? Is it good? Where can I find a sample or > tutorial of this architecture I'm proposing? > > Thanks in advance. > > -- > View this message in context: > http://www.nabble.com/Need-help-with-activemq---php-architecture-tp23525164p23525164.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
