raketka: distributed-process node

[ library, network-control, program, public-domain ] [ Propose Tags ]

peer node with simplelocalnet backend

[Skip to Readme]
Versions 1.0, 1.1, 1.1.1, 1.1.2
Change log changelog.md
Dependencies aeson, async, base (>=4.8 && <5.0), binary, bytestring, conf-json, containers, distributed-process, distributed-process-simplelocalnet, network, network-transport, network-transport-tcp, random, stm, tagged, template-haskell [details]
License LicenseRef-PublicDomain
Author Imants Cekusins
Maintainer Imants Cekusins
Category Network Control
Home page https://github.com/ciez/raketka
Source repo head: git clone https://github.com/ciez/raketka.git
Uploaded by procione at Thu Jul 12 11:27:07 UTC 2018
Distributions NixOS:1.1.2
Executables raketka
Downloads 666 total (30 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2018-07-12 [all 1 reports]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for raketka-1.1.2

[back to package description]


* basic distributed-process node
* configurable peers

Begin reading at Control.Distributed.Raketka.Type.Arg

see also: 

    *   [parconc-examples](https://hackage.haskell.org/package/parconc-examples)
    *   [haskell-distributed tutorials](http://haskell-distributed.github.io/tutorials/1ch.html)  

This library: 

        * start nodes 
        * connect them with each other
        * exchanges pings with other nodes which are expected to pong back
        * received pings & pongs are output to stdout
        * when 1 node is disconnected or stops, the other nodes stdout notifications about this

    may be extended 
    however you are most likely to write your own code that does much more. 

    is simple on purpose, does only a few things which seem to be common in distributed arch 

To start the program that comes with this library:

    start the same program in multiple consoles: 1 per node
    2 args are expected:

        1. path to config.json (see test-conf.json)
        2. idx of this node in the cluster: 0 .. (length Cluster -1)