High-performance, non-blocking architecture for the next generation of event-driven messaging applications.
JMS 1.1 & 2.0 with full client implementation including JNDI High availability using shared storage or network replication Simple & powerful protocol agnostic addressing model Flexible clustering for distributing load Advanced journal implementations for low-latency persistence as well as JDBC High feature parity with ActiveMQ 5 to ease migration
Apache ActiveMQ Artemis alternatives and similar libraries
Based on the "Messaging" category.
Alternatively, view Apache ActiveMQ Artemis alternatives based on common mentions on social networks and blogs.
9.8 9.9 L2 Apache ActiveMQ Artemis VS Apache KafkaHigh-throughput distributed messaging system.
Apache RocketMQ™ is an open source distributed messaging and streaming data platform.
Distributed pub/sub-messaging system.
9.1 10.0 L3 Apache ActiveMQ Artemis VS Apache CamelGlues together different transport APIs via Enterprise Integration Patterns.
8.6 9.9 L4 Apache ActiveMQ Artemis VS AeronEfficient reliable unicast and multicast message transport.
8.1 8.6 L2 Apache ActiveMQ Artemis VS Apache ActiveMQMessage broker that implements JMS and converts synchronous to asynchronous communication.
5.2 8.0 L5 Apache ActiveMQ Artemis VS HermesFast and reliable message broker built on top of Kafka.
Clear, concise, modular and made to be embedded.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Apache ActiveMQ Artemis or a related project?
This file describes some minimum 'stuff one needs to know' to get started coding in this project.
For details about the modifying the code, building the project, running tests, IDE integration, etc. see our [Hacking Guide](./docs/hacking-guide/en/SUMMARY.md).
Building the ASYNC IO library
ActiveMQ Artemis provides two journal persistence types, NIO (which uses the Java NIO libraries), and ASYNCIO which interacts with the linux kernel libaio library. The ASYNCIO journal type should be used where possible as it is far superior in terms of performance.
ActiveMQ Artemis does not ship with the Artemis Native ASYNCIO library in the source distribution. These need to be built prior to running "mvn install", to ensure that the ASYNCIO journal type is available in the resulting build. Don't worry if you don't want to use ASYNCIO or your system does not support libaio, ActiveMQ Artemis will check at runtime to see if the required libraries and system dependencies are available, if not it will default to using NIO.
To build the ActiveMQ Artemis ASYNCIO native libraries, please follow the instructions in the artemis-native/README.
Our documentation is always in sync with our releases at the Apache ActiveMQ Artemis website.
Or you can also look at the current master version on github.
To run an example firstly make sure you have run
$ mvn -Prelease install
If the project version has already been released then this is unnecessary.
Each individual example can be run using this command from its corresponding directory:
$ mvn verify
If you wish to run groups of examples then use this command from a parent directory (e.g. examples/features/standard):
$ mvn -Pexamples verify
Recreating the examples
If you are trying to copy the examples somewhere else and modifying them. Consider asking Maven to explicitly list all the dependencies:
# if trying to modify the 'topic' example: cd examples/jms/topic && mvn dependency:list
Open Web Application Security Project (OWASP) Report
If you wish to generate the report for CCV dependencies, you may run it with the -Powasp profile
$ mvn -Powasp verify
The output will be under ./target/dependency-check-report.html for each sub-module.