Software Engineer III at a financial services firm with 10,001+ employees
Real User
Top 5
Jun 4, 2025
ActiveMQ inside AP is one of those powerful features because we generally use ActiveMQ for acting on incidents which do not involve any human interaction or personal activity. For example, you have to act on some response which is being received by another third-party system, and we totally have no idea when that response would be coming. In that case, you can set up an ActiveMQ, and whenever any message gets sent to that ActiveMQ it can react based on your configurations, and you can trigger some processes, calls, or signals. ActiveMQ is beneficial in cases where we do not know when the response will come and when we do not know who is sending that response. We do not know the sender, sending time, or message type. In such cases, we can configure multiple MQs and configure actions for them. Depending on the message body, sender, type of message, and timing, it will react. This reduces human interactions and manpower efficiency efforts.
We have a digital ID platform that uses various services running on Kafka. There are two main endpoints where services interact with external services. These include an automatic biometric service (Avis) and a print service, among others. ActiveMQ is used to manage the flow of registration data and interact with these services.
Lead Data Engineer at a energy/utilities company with 51-200 employees
Real User
May 2, 2024
We often work on message transfer between sensors. An IoT device sends a message about a sensor failure to the database. Before inserting into the database, the failure message is sent to ActiveMQ, and that uses a Python script to insert it to the internal database.
We use ActiveMQ for message brokering in our architecture. It is a central hub where we publish codes like city codes and office IDs for our server application. Other applications subscribe to relevant topics on ActiveMQ to receive and consume these messages, ensuring they stay updated with the latest code information.
Senior Software Engineer at a retailer with 10,001+ employees
Real User
Aug 30, 2023
We used it for communication between microservices. For example, if service one makes an update and service two needs to be aware of it, and it doesn't need to be synchronous, it can handle that later as well.
Technology Lead at a tech services company with 10,001+ employees
MSP
Jun 22, 2023
We use the solution to manage the event messages by controlling the flow rate, handling error resubmissions, and ensuring the controlled processing of events.
ActiveMQ is the middleware to consume the payloads because some applications are incapable of consuming APIs and other such things. Alternatively, they may want to send an offline message once the process is complete, and then put that message into ActiveMQ for the middleware application to consume.
ActiveMQ is a messaging broker facilitating microservices communication and event management. It supports message queues, Camel routes, and asynchronous communication, enhancing integration capabilities and scalability with a network of brokers.ActiveMQ efficiently supports message transfer in IoT applications and third-party systems, acting as a hub for code distribution and data flow management. It integrates well with XML and protocols like MQTT, while its fast messaging, reliable...
In my current organization, I'm only working with ActiveMQ. I previously worked with IBM WebSphere MQ.
ActiveMQ inside AP is one of those powerful features because we generally use ActiveMQ for acting on incidents which do not involve any human interaction or personal activity. For example, you have to act on some response which is being received by another third-party system, and we totally have no idea when that response would be coming. In that case, you can set up an ActiveMQ, and whenever any message gets sent to that ActiveMQ it can react based on your configurations, and you can trigger some processes, calls, or signals. ActiveMQ is beneficial in cases where we do not know when the response will come and when we do not know who is sending that response. We do not know the sender, sending time, or message type. In such cases, we can configure multiple MQs and configure actions for them. Depending on the message body, sender, type of message, and timing, it will react. This reduces human interactions and manpower efficiency efforts.
We have a digital ID platform that uses various services running on Kafka. There are two main endpoints where services interact with external services. These include an automatic biometric service (Avis) and a print service, among others. ActiveMQ is used to manage the flow of registration data and interact with these services.
We often work on message transfer between sensors. An IoT device sends a message about a sensor failure to the database. Before inserting into the database, the failure message is sent to ActiveMQ, and that uses a Python script to insert it to the internal database.
We use ActiveMQ for message brokering in our architecture. It is a central hub where we publish codes like city codes and office IDs for our server application. Other applications subscribe to relevant topics on ActiveMQ to receive and consume these messages, ensuring they stay updated with the latest code information.
We used it for communication between microservices. For example, if service one makes an update and service two needs to be aware of it, and it doesn't need to be synchronous, it can handle that later as well.
We use the solution to manage the event messages by controlling the flow rate, handling error resubmissions, and ensuring the controlled processing of events.
The primary use case of this solution is to send messages between applications.
ActiveMQ is the middleware to consume the payloads because some applications are incapable of consuming APIs and other such things. Alternatively, they may want to send an offline message once the process is complete, and then put that message into ActiveMQ for the middleware application to consume.
We are using ActiveMQ in our customers' companies, so all of the integrations are there. We use this solution for microservices intercommunication.
We use this solution for messaging.