It’s interesting to see people getting interested in porting the Disruptor to .NET (although what’s wrong with The One True Language, I don’t know!).
- Tim Gebhardt has a port on Github
- Matt Davey (Technical Director at Lab49) also has a couple of posts about porting the Disruptor and comparing the performance of his port to the Java version
I’ll try to keep this post updated as I learn of more .NET interest. Alternatively, please feel free to post a comment below.
Share this:
#1 by Rory on September 26, 2011 - 9:12 pm
Quote
“The One True Language”, yes that’d be C
#2 by Rory on September 26, 2011 - 9:30 pm
Quote
I’ve been reading up on Disruptor, and fully understand circular buffers etc (being an old C hacker)
I’m having a hard time trying to think the problem thro’ of an enterprise solution. It appears from the documentation (and I’m probably wrong here) that Disruptor operates in an application or a single app domain.
How would I go about using this across the wire e.g. A Silverlight client , or any client for that matter ?
Would the consumer be a server component pushing messages over the wire to the SL client, WCF, TCP or whatever, obviously latency bound by doing that.
I’ve looked at the unit tests in the .NET port, fine, but still can’t get my head around a possible “enterprise” solution.
Hope this makes some sort of sense, or am I barking up the wrong tree ?
#3 by Danny on October 6, 2011 - 11:24 pm
Quote
Hi Rory. Sorry for the late response – I only just found your comments among the sea of spam!
The Disruptor is a Java framework for passing messages between threads within an application. In LMAX, it also forms the basis of our interprocess messaging, but only in the sense that it sits at the boundary of each server and we use it to hand of messages between our message bus and the business logic.
I would recommend the Google Group for the Distruptor (at http://groups.google.com/group/lmax-disruptor) if you haven’t already found it.