# Disruptor, Now Open Source!

DevFeed: [Disruptor, Now Open Source!](<https://devfeed.tech/articles/disruptor-now-open-source-30634.md>)

Original publisher: [Read original article](<http://bad-concurrency.blogspot.com/2011/06/disruptor-now-open-source.html>)

Author: Michael Barker (noreply@blogger.com)

Published: 2011-06-22T15:07:00Z

Content type: article

Language: en

Sources: [Bad Concurrency](<https://devfeed.tech/sources/bad-concurrency.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Code](<https://devfeed.tech/topics/code.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Java](<https://devfeed.tech/topics/java.md>), [QCon Software Development Conference](<https://devfeed.tech/topics/qcon-software-development-conference.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [java](<https://devfeed.tech/tags/java.md>), [latency](<https://devfeed.tech/tags/latency.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [performance](<https://devfeed.tech/tags/performance.md>), [queue](<https://devfeed.tech/tags/queue.md>)

## AI overview

The article announces that the Disruptor, a ring-buffer-based design pattern used at the core of an LMAX financial exchange, has been open sourced. It describes the Disruptor as an alternative to a queue or a simple actor-like concurrency framework, and reports higher throughput and lower latency than Java's ArrayBlockingQueue.

## Source excerpt

The Disruptor, the design pattern at the core of the financial exchange I'm helping build at LMAX has been open sourced. If you've seen the presentation that Martin Thompson and I gave at QCon or the one I did for the LJC @Skillsmatter, this is the ring-buffer based code that we've been banging on about for a while. What is the Disruptor? At its simplest, it's an alternative to a queue, but can also can be thought of as a simple actor-like concurrency framework. Why? Performance, it's about 8-9 times higher throughput and 3 orders of magnitude lower latency than Java's ArrayBlockingQueue. There's a technical article on the Google code site with more details of the implementation and comprehensive performance test results.