Libraries
AMQP for Java. Reliable publishing with confirms, retries the broker enforces,
dead-letter and parking queues with replay, streams, pipelines, ordered
consumption, and five serialization formats.
Runnable, self-contained examples for the Java library — each one compiled and
run against a real broker in CI, so none of them rots quietly.
Ports planned
Go, .NET, Python, Rust and TypeScript, once the wire behaviour is pinned down by a
shared specification and conformance suite. Nothing exists yet — this is a statement
of intent, not a roadmap with dates.
Using the Java library
<repositories>
<repository>
<id>acemq</id>
<url>https://acemq-company.github.io/maven/</url>
</repository>
</repositories>
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-amqp-core</artifactId>
<version>0.2.4</version>
</dependency>
<dependency>
<groupId>org.acemq</groupId>
<artifactId>acemq-transport-rabbitmq</artifactId>
<version>0.2.4</version>
<scope>runtime</scope>
</dependency>
Both are needed. The transport is discovered at runtime from the
amqp:// scheme in your URL, so your code never compiles against it —
but without it on the classpath a connection fails with
no transport for scheme amqp.
Artifacts
Everything published under org.acemq, with sources and Javadoc, readable
without credentials. Not Maven Central yet: that is permanent, and coordinates are
still settling before 1.0.
Support
Architecture review, production readiness, TLS and permission design, and incident
response for RabbitMQ and for these libraries. The libraries are complete and free to
use without it, and are not crippled to sell it.