3 ms·
Interesting choice, wonder why they didnt go with Apache Apollo which is supposed to be the successor to ActiveMQ, or newer systems like RocketMQ or Apache Puls
by manigandham 9y ago
Interesting choice, wonder why they didnt go with Apache Apollo which is supposed to be the successor to ActiveMQ, or newer systems like RocketMQ or Apache Pulsar.
- discodave 9y agoMy guess: Market share. Go where the $$$ is. For AWS, if they were thinking about Apollo, they would be more likely to try and out-compete it before it gets a foothold.
- Zaheer 9y agoThey're targeting the massive existing customer base for ActiveMQ, from the blog post: "SQS and SNS have been used extensively for applications that were born in the cloud. However, many of our larger customers are already making use of open-sourced or commercially-licensed message brokers."
- talawahdotnet 9y agoI believe Apollo was abandoned in favor of Artemis[1] which is based on RedHat's donation of HornetQ. But yea, the community doesn't seem to have rushed to adopt Artemis so it looks like AWS is starting where the numbers are. The Amazon MQ UI specifically mentions which "Engine" is being used so hopefully there will be other options in the future. Similar to how RDS and Elasticache support multiple DB/Cache Engines. 1. https://activemq.apache.org/artemis/ https://activemq.apache.org/artemis/