<p>Here is a technical paper on the LMAX Architecture (I just followed a link found on the blog you linked here): <a href="http://disruptor.googlecode.com/files/Disruptor-1.0.pdf" rel="nofollow noreferrer">http://disruptor.googlecode.com/files/Disruptor-1.0.pdf</a></p>
<p>As the website is long gone, here is a version I dug up using the Wayback Machine: <a href="https://drive.google.com/file/d/1tw1Pql7ge54Q_D4gSMeXVONVM7Xyg34c/view?usp=sharing" rel="nofollow noreferrer">https://drive.google.com/file/d/1tw1Pql7ge54Q_D4gSMeXVONVM7Xyg34c/view?usp=sharing</a></p>
<p>The multicast graph example is at page 9 of this PDF is as follows:</p>
<p><a href="https://i.sstatic.net/65aGr2HB.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/65aGr2HB.png" alt="Multicast graph" /></a></p>
<p><em>Note that the letters P and C represents Producer and Consumer respectively.</em></p>
<p>There are also examples of multicast graphs (compared to various other options) here: <a href="http://en.wikipedia.org/wiki/Multicast" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Multicast</a></p>

CC BY-SA 4.0
2021-07-02T09:02:33.560Z
The link does not work.
amer
CC BY-SA 4.0
2011-07-21T04:21:20.680Z
2024-11-26T09:50:44.440Z
2024-11-26T09:50:44.440Z
Daniel Apon
<p>Martin Fowler in his blog post on "<a href="http://martinfowler.com/articles/lmax.html" rel="nofollow">The LMAX Architecture</a>" tried to describe the component called Disruptor as a multicast graph of queues</p>

<blockquote>
  <p>At a crude level you can think of a Disruptor as a multicast graph of
  queues where producers put objects on it that are sent all the
  consumers for parallel consumption through separate downstream
  queues...</p>
</blockquote>

<p>I'm having difficulties understanding the nature of a multicast graph</p>

CC BY-SA 3.0
2011-07-20T13:46:52.303Z
This question currently doesn't have enough information to get a good answer (which is why it seems to have been downvoted by one person, though downvoting without leaving a comment is discouraged here). Can you link to the blog post you're referring to, at a minimum? Also, "I'm having difficulties understanding the nature" is a bit too vague - it's necessary to ask at least a somewhat more specific question, or else this might be better as a comment to the blog post than a post on CSTheory :-).
Rob Simmons
CC BY-SA 3.0
2011-07-20T18:27:03.610Z
Thanks for adding the link. "Multicast graph" isn't anything I know about personally, but the authors do indeed talk about it like it's some standard data structure/networking thingamagig. Hopefully someone else here can help you!
Rob Simmons
CC BY-SA 3.0
2011-07-20T18:28:43.760Z
@Rob Simmons I downvote without comment with using my smart phone since it would take too long to enter the comment. I downvoted because I don't think this is research level.
Tyson Williams
CC BY-SA 3.0
2011-07-20T18:38:48.800Z
@Tyson I'm not sure the (edited) question is not-research-level, though it's probably borderline. The blog post uses the term "multicast graph" as if it's a generalization of the specific thing being considered, the term is not easily Wikipedia-able, and the first matches on Google aren't helpful. (We're allowed to disagree, of course :-).)
Rob Simmons
<graph-theory><queueing-theory>
What is a multicast graph?
Boris Pavlović
# What is a multicast graph?

(Asked by: username_0 on 2011-07-20)

Martin Fowler in his blog post on "[The LMAX Architecture](http://martinfowler.com/articles/lmax.html)" tried to describe the component called Disruptor as a multicast graph of queues

> At a crude level you can think of a Disruptor as a multicast graph of
> queues where producers put objects on it that are sent all the
> consumers for parallel consumption through separate downstream
> queues...

I'm having difficulties understanding the nature of a multicast graph

**Tags:** graph-theory, queueing-theory

> **Comments:**
> **username_1**: This question currently doesn't have enough information to get a good answer (which is why it seems to have been downvoted by one person, though downvoting without leaving a comment is discouraged here). Can you link to the blog post you're referring to, at a minimum? Also, "I'm having difficulties understanding the nature" is a bit too vague - it's necessary to ask at least a somewhat more specific question, or else this might be better as a comment to the blog post than a post on CSTheory :-).  
> **username_1**: Thanks for adding the link. "Multicast graph" isn't anything I know about personally, but the authors do indeed talk about it like it's some standard data structure/networking thingamagig. Hopefully someone else here can help you!  
> **username_2**: @username_1 I downvote without comment with using my smart phone since it would take too long to enter the comment. I downvoted because I don't think this is research level.  
> **username_1**: @Tyson I'm not sure the (edited) question is not-research-level, though it's probably borderline. The blog post uses the term "multicast graph" as if it's a generalization of the specific thing being considered, the term is not easily Wikipedia-able, and the first matches on Google aren't helpful. (We're allowed to disagree, of course :-).)  

---

## 1 answers

### Answer by username_3 on 2011-07-21. Score: 8 | Accepted answer

Here is a technical paper on the LMAX Architecture (I just followed a link found on the blog you linked here): <http://disruptor.googlecode.com/files/Disruptor-1.0.pdf>

As the website is long gone, here is a version I dug up using the Wayback Machine: <https://drive.google.com/file/d/1tw1Pql7ge54Q_D4gSMeXVONVM7Xyg34c/view?usp=sharing>

The multicast graph example is at page 9 of this PDF is as follows:

[![Multicast graph](https://i.sstatic.net/65aGr2HB.png)](https://i.sstatic.net/65aGr2HB.png)

*Note that the letters P and C represents Producer and Consumer respectively.*

There are also examples of multicast graphs (compared to various other options) here: <http://en.wikipedia.org/wiki/Multicast>

> **Comments:**
> **username_4**: The link does not work.  

---

