Apache ActiveMQ is recommended for enterprises looking for a reliable and scalable message broker, developers needing rich messaging functionality, and organizations that require robust support for various messaging protocols, including JMS, AMQP, STOMP, and MQTT. It is particularly well-suited for applications that need to distribute messages between different applications, languages, and platforms.
No Apache ActiveMQ videos yet. You could help us improve this page by suggesting one.
Based on our record, Apache Thrift should be more popular than Apache ActiveMQ. It has been mentiond 13 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I once read a paper about Apache/Meta Thrift [1,2]. It allows you to define data types/interfaces in a definition file and generate code for many programming languages. It was specifically designed for RPCs and microservices. [1]: https://thrift.apache.org/. - Source: Hacker News / 8 months ago
While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / over 1 year ago
Services in general communicate via Thrift (and in some cases HTTP). Source: about 2 years ago
Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 2 years ago
RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: over 2 years ago
Before Kafka, traditional message queues like RabbitMQ and ActiveMQ were widely used, but they had limitations in handling massive, high-throughput real-time data streams. - Source: dev.to / 4 months ago
Consume open-source queuing services – customers can deploy message brokers such as ActiveMQ or RabbitMQ, to develop asynchronous applications, and when moving to the public cloud, use the cloud providers managed services alternatives. - Source: dev.to / 4 months ago
Apache ActiveMQ is an open-source Java-based message queue that can be accessed by clients written in Javascript, C, C++, Python and .NET. There are two versions of ActiveMQ, the existing “classic” version and the next generation “Artemis” version, which is currently being worked on. - Source: dev.to / about 2 years ago
For real-time streaming, we have other frameworks and tools like Apache Kafka, ActiveMQ, and AWS Kinesis. - Source: dev.to / over 2 years ago
The back-end is designed as a set of microservices communicating through a message broker, ActiveMQ, with a custom configuration to support delayed delivery and other features. - Source: dev.to / almost 3 years ago
Docker Hub - Docker Hub is a cloud-based registry service
RabbitMQ - RabbitMQ is an open source message broker software.
Eureka - Eureka is a contact center and enterprise performance through speech analytics that immediately reveals insights from automated analysis of communications including calls, chat, email, texts, social media, surveys and more.
IBM MQ - IBM MQ is messaging middleware that simplifies and accelerates the integration of diverse applications and data across multiple platforms.
Traefik - Load Balancer / Reverse Proxy
Apache Kafka - Apache Kafka is an open-source message broker project developed by the Apache Software Foundation written in Scala.