gochan

中文说明文档

background

In general, a buffered channel variable is defined with a dedicated goroutine to execute the specific events in channel.

If there are so many events that a single gorotine is not enough, may more goroutines are created to execute events. However, it is not okey if some events need to be executed sequentially.

Two events, for example, one order payment and goods delivery of that order, need to be executed sequentially. At the same time, events of different orders can be executed concurrently. So that we can push events of the same order to the same buffer channel, and a specific goroutine to execute the events in the queue.

Concurrency is achieved by expanding multiple similar combinations (a buffer channel and its specific goroutine) in parallel.

Usual design

a buffered channel variable is defined with a dedicated goroutine to execute the specific events in channel

event ->
        |
event -> buffer-channel -> goroutine
        |
event ->

State-independent concurrent design

There is no state dependency between events, so you can simply extend goroutine to speed up event execution.

event ->                 ->goroutine
        |               |
event -> buffer-channel -> goroutine
        |               |
event ->                 ->goroutine

State-dependent concurrent design (as gochan does)

Introduce a layer of dispatcher to distribute events to the corresponding buffer-channel according to a feature such as uuid.

event ->              -> buffer-channel -> goroutine
        |            |
event --> dispatcher -> buffer-channel -> goroutine
        |            |
event ->              -> buffer-channel -> goroutine

example

you can find example in examples.