What is this?
LMAX Disruptor is a Java library for high-performance messaging between threads inside a single application — very fast in-process event passing.
LMAX Disruptor is a Java library for high-performance messaging between threads inside a single application — very fast in-process event passing.Is it a library I add to my own Java project, or something I deploy as a server?A library: you add it as a dependency to your own Java project and use it inside your process — there is no server or daemon to deploy.
A library: you add it as a dependency to your own Java project and use it inside your process — there is no server or daemon to deploy.How do I add it to a project and start using it?Start with the Guide and documentation the README links — they walk through the programming model; then wire the library into your Gradle or Maven build.
Start with the Guide and documentation the README links — they walk through the programming model; then wire the library into your Gradle or Maven build.Do I need anything besides a JDK to run it?Just a JDK — it is pure Java with no native components or external services; the project's own CI builds it with Gradle.
Just a JDK — it is pure Java with no native components or external services; the project's own CI builds it with Gradle.So it wires threads together inside one app — it doesn't send messages between machines or services?Right — its scope is inter-thread messaging within one JVM. It is not a network broker and won't carry messages between machines or services.
Right — its scope is inter-thread messaging within one JVM. It is not a network broker and won't carry messages between machines or services.What kind of applications is it built for?Latency-sensitive Java systems — it comes from the LMAX Exchange team, so think in-process pipelines where throughput and latency matter more than convenience.
Latency-sensitive Java systems — it comes from the LMAX Exchange team, so think in-process pipelines where throughput and latency matter more than convenience.Is the concurrency actually stress-tested, or do I just have to trust it?CI runs Java Concurrency Stress (jcstress) suites — a quick pass plus a manual deep run — alongside Gradle builds and CodeQL analysis.
CI runs Java Concurrency Stress (jcstress) suites — a quick pass plus a manual deep run — alongside Gradle builds and CodeQL analysis.Can I use it in commercial software?Yes — it is Apache-2.0 licensed, a permissive license, so it is free to use in commercial products.
Yes — it is Apache-2.0 licensed, a permissive license, so it is free to use in commercial products.Is this battle-tested infrastructure or a recent experiment?Established: the repository dates back to 2012 and the project is maintained by the LMAX Development Team, with stress tests wired into CI.
Established: the repository dates back to 2012 and the project is maintained by the LMAX Development Team, with stress tests wired into CI.What are similar projects?EventBus, tokio, redisson, sidekiq, miaosha, caffeine, muduo, Android-Universal-Image-Loader
EventBus, tokio, redisson, sidekiq, miaosha, caffeine, muduo, Android-Universal-Image-LoaderWhich topics is it in?asynchronous, low-latency, gradle, event-driven, multithreading, jvm, messaging, concurrency, high-performance, developers, java, performance
asynchronous, low-latency, gradle, event-driven, multithreading, jvm, messaging, concurrency, high-performance, developers, java, performance