alice-go / fer

a Go-based reimplementation of FairMQ

fer

fer is a simple reimplementation of FairMQ in Go.

License

fer is released under the BSD-3 license.

Installation

fer is installable via go get:

$> go get github.com/alice-go/fer/...

NOTE: you need at least go1.7.

Documentation

Documentation is available on godoc.

Examples

Testing example-2 from FairMQ tutorial

## terminal 1
$> fer-ex-sink --id sink1 --mq-config ./_example/cmd/testdata/ex2-sampler-processor-sink.json

## terminal 2
$> fer-ex-processor --id processor --mq-config ./_example/cmd/testdata/ex2-sampler-processor-sink.json

## terminal 3
$> fer-ex-sampler --id sampler1 --mq-config ./_example/cmd/testdata/ex2-sampler-processor-sink.json

This will run 3 devices, using the ZeroMQ transport.

To run with nanomsg as a transport layer, add --transport nanomsg to the invocations.

fer's Issues

implement native Go ZeroMQ transport

• implement push/pull (go-zeromq/zmq4#9)
• implement req/rep (go-zeromq/zmq4#9)
• implement dealer/router (go-zeromq/zmq4#9)
• implement pub/sub (go-zeromq/zmq4#9)
• implement xpub/xsub (go-zeromq/zmq4#9)
• implement pair (go-zeromq/zmq4#9)
• implement bus (go-zeromq/zmq4#9)
• implement multi-part messages (go-zeromq/zmq4#9)

O² Control support

Following up on alisw/alidist#1230 (comment)

The O² Control executor supports both FairMQ and Direct control modes, so it can be configured to send either:

• FairMQ-specific state machine events to the OCC plugin of a running FairMQ device, or
• "uncooked" Control state machine events with no FairMQ-specific handling to any other process with a compatible gRPC server.

No such process-side implementation exists yet (we only have FairMQPlugin_OCC) so this Direct non-FairMQ code path in O² Control is untested, and fer can be a candidate. Alternatively it could also make sense to keep fer's interface completely FairMQ compatible, use the FairMQ control mode and rather reimplement the equivalent to FairMQPlugin_OCC in fer.

In one way or another, the fer device should implement a gRPC server for this or a similar protofile, including a mechanism for defining channels and setting properties during (re)configuration.

See controlmode and occplugin.

more protocols/transports

investigate https://github.com/Jeffail/benthos for more transports/protocols and how to mesh them.
(also: API)