search

c-cube / frog-utils

[frozen] Scheduling and running jobs on a shared computer, then analyse their output
BSD 2-Clause "Simplified" License
5 stars 0 forks source link

use nanomsg to communicate #23

Closed c-cube closed 7 years ago

c-cube commented 9 years ago

More interesting possibilities of communication.

pattern: each tool has one Bus socket on a common \Ipc "frog"` address. Interesting events (mainly "job is finished" are broadcasted.)

Opens up the possibility of splitting tools into microservices; e.g., a mail or IRC notifier would be a separate tool (with its own dependencies), and it would listen on the Bus socket for interesting news.

Gbury commented 9 years ago

We would most likely need a module that defines a type along with encoders/decoders for the messages passed on this bus. The question would then be where to put that module ? Separate frog-messages lib ? or in frog-utils ?

c-cube commented 9 years ago

in frog-utils, like the rest --- using JSON messages with ppx_deriving.