activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: Messaging protocol selection
Date Tue, 08 Oct 2013 19:22:27 GMT
Using the default protocol (Openwire) for Java.
Use STOMP for your PHP needs.

Apollo has had some good community use. It's not a feature-complete drop-in
replacement for ActiveMQ 5.x yet, but should be suitable for the needs you
describe above.

Apollo also supports Openwire and STOMP protocols.




On Mon, Oct 7, 2013 at 5:05 AM, Marko Asplund <marko.asplund@gmail.com>wrote:

> Hi,
>
> I'm planning on deploying ActiveMQ for delivering event notifications
> across different applications and web sites.
> The events will be delivered to multiple recipients using publish-subscribe
> pattern.
> The number of clients is expected to be about 10-20 and they will be
> connecting over the Internet.
> Message will contain mostly textual data e.g. XML and the typical message
> size is estimated to be ~ 50 - 100 bytes.
> Message volumes are expected to be moderate.
> The clients will be implemented using different technologies, so cross
> language interoperability will be important.
> In particular, both Java and PHP should be well supported.
> XA transactions will not be required, but durable subscriptions and message
> expiry are features that may be needed.
>
> Which messaging protocols would be good choices in this case?
> Can different clients be allowed to use different protocols to communicate
> through the same topic?
>
> Is Apollo currently mature enough to be considered as an alternative to
> ActiveMQ?
>
>
>
>
> thanks,
>
> marko
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message