0 vs 382: Third-Party Code in Your Messaging Stack
Aeron® 1.54.1 ships zero third-party runtime dependencies on the client and on the Media Driver, Archive and Cluster. Its only other package, Agrona, comes from the same vendor. At the other end, the AutoMQ 1.7.4 distribution bundles 382 third-party jars and the Pulsar 5.0.1 broker resolves to 282. Every one of them is code you did not write, running in a process that holds your order flow. All of them need CVE tracking, licence review and patching. Two traps hide part of the count from scanners: shaded client jars, which declare few or no dependencies and bundle the rest, and test libraries declared at compile scope.
How the dependencies were counted
Section titled “How the dependencies were counted”Third-party runtime dependencies by framework, client and server
Section titled “Third-party runtime dependencies by framework, client and server”Aeron: zero third-party dependencies on client and server
Section titled “Aeron: zero third-party dependencies on client and server”Chronicle Queue: 11 dependencies and a default-on analytics client
Section titled “Chronicle Queue: 11 dependencies and a default-on analytics client”Shaded client jars hide their dependencies from scanners
Section titled “Shaded client jars hide their dependencies from scanners”Test libraries that reach the production classpath
Section titled “Test libraries that reach the production classpath”Broker servers: where the hundreds of jars come from
Section titled “Broker servers: where the hundreds of jars come from”Settings that shrink the footprint
Section titled “Settings that shrink the footprint”What this comparison does not cover
Section titled “What this comparison does not cover”This site is not affiliated with, endorsed by, or sponsored by Adaptive Financial Consulting Limited or the Aeron project. Aeron is a registered trademark of Adaptive Financial Consulting Limited.
Aeron is a trademark of Adaptive Financial Consulting Limited in the United Kingdom and other countries.