Ask : Is Go-Disruptor ready / safe for production ? or Is there any inprogress job ?

[devararendy]

Hi @joliver, i'm very interested to use LMAX Disruptor in Golang.
But i would like to know whether this library is ready / safe for Production or is there any inprogress job ?
Previously I'm using ported LMAX Disruptor in C++

So it's very interesting to use Disruptor in Go.

Thank You

[joliver]

Unfortunately using Go code this isn't possible due to the Go Memory Model. The only solution would be to write processor-specific assembly code that creates the appropriate write/read memory barriers.

Further, now that Go has generics, it would be easier to hold the RingBuffer[T] inside of the Disruptor.

Again, this is not anywhere close to being ready for production.

[sshelll]

Unfortunately using Go code this isn't possible due to the Go Memory Model. The only solution would be to write processor-specific assembly code that creates the appropriate write/read memory barriers.

Hi @joliver , I would like to know the reason why this component can't be used in the production environment.

Is it because the go-mem-model limits the implementation of multiple producers?

Or is there just a possible problem with the current version(single-producer : multi-consumer)?