activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <>
Subject Re: Amazon MQ
Date Fri, 08 Dec 2017 14:21:13 GMT
I made some inquiries and have it on good authority that the AWS Managed 
ActiveMQ effort was started part of the RH partnership [1]. So while the 
community was not contacted, AWS did talk to people with ActiveMQ 
expertise. Now I am surprised that the RH people on this list didn't 
know about it (and given the inquiries I really believe they were not 
aware of that). RH is a large company and it looks like opinions 
(regarding ActiveMQ) are as diverse as they are in this community.

Related to AWS, this was not a whim, an "it would be nice" sort of 
service. They have serious interest from users. There is massive (and 
increasing) interest in asynchronous messaging (see also Kafka, 
RabbitMQ). People make serious investments in such systems and the 
credibility of the community is super important.



On 11/28/2017 10:51 PM, Justin Bertram wrote:
> I saw that announcement as well and was a bit puzzled by the lack of any
> involvement by Amazon in the community (at least that I could tell).  That
> is, of course, their prerogative.
> Since it's so unclear at this point how this potentially new user-base
> might impact the community I don't see how it can factor in to the
> road-map.  It may complicate things; it may not.  There may be renewed
> interest in 5.x; there may not.  Who's to say?  In my opinion this further
> highlights the need to clearly define a project road-map.  If such a
> road-map had been defined 6-12 months ago maybe Amazon is making a
> different announcement today.
> Justin
> On Tue, Nov 28, 2017 at 9:32 PM, Tim Bain <> wrote:
>> Amazon announced today a service called Amazon MQ that allows ActiveMQ 5.x
>> to be run as a managed service in AWS:
>> broker-service-for-activemq/
>> Was anyone on this list aware of that effort prior to this announcement?
>> We should all be aware that there may be additional users coming to
>> ActiveMQ as a result of this service, who may have minimal experience with
>> the configuration details of the broker and limited access to detailed
>> troubleshooting information such as logs and JMX. This may complicate or
>> delay the eventual sunsetting of 5.x in favor of Artemis; there may be
>> interest in keeping 5.x alive for longer as a result of its use in this
>> service.
>> Tim

View raw message