ActiveMQ offers network of brokers for scalability, consistent queue names, valuable Docker images, multi-protocol support including MQTT, load balancing, and failover protocols. Users appreciate fast asynchronous messaging, message durability, ease of setting up persistent messages, JMS integration, lightweight nature, data transfer flexibility, and XML interaction. High availability, reliable delivery, message persistency, latency management, and integration capability also stand out. Users find Docker setups quick and appreciate its efficient handling and easy configuration.
- "The initial setup and first deployment of ActiveMQ is fairly simple."
- "We value ActiveMQ for its performance, throughput, and low latency, especially in handling large volumes of data and sequential management of topics."
- "The main function I find valuable in ActiveMQ is facilitating message transfer within the client's internal network. ActiveMQ handles the message transfer from the internal network to the cloud. Regarding multi-protocols, we use different approaches based on client capabilities. Some clients connect for real-time data transfer, using database queries for periodic updates every ten minutes. We collect data from multiple clients, ensuring we get real-time sensor values where possible and periodic updates for others."
ActiveMQ faces challenges in message management, protocol support, and clustering. Its admin tools and UI need improvements for ease of use and functionality. Users find setup and configuration complex, leading to stability issues. ActiveMQ lacks efficient multi-platform client support, particularly for non-Java languages. Enhancements are required in monitoring tools and scalability features. Documentation on advanced topics is insufficient, and the current monitoring tools are basic, limiting visibility into system status.
- "Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks."
- "We need to enhance stability and improve the deployment optimization to fully leverage the platform's capabilities."
- "For additional functionality, I suggest making it easier to install and monitor the queues, topics, broker status, publisher status, and consumer status. Improved monitoring tools would help avoid needing to manually access the server for monitoring purposes."