raketka: basic distributed-process node with configurable peers

[ library, network-control, program, public-domain ] [ Propose Tags ]
This version is deprecated.
Versions [RSS] 1.0, 1.1, 1.1.1, 1.1.2, 1.1.3 (info)
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 2016-12-11T18:09:12Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Executables raketka
Downloads 2209 total (14 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for raketka-1.0

[back to package description]

raketka

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 has basic working code 
to enable to start nodes and to connect them with each other. 

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

This library is simple on purpose. 
It took me a few days to write this code and make it work.    

To start the program that comes with this library:

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

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

The program exchanges pings with other nodes which are expected to pong back. 
Both pings & pongs are output to stdout

When you shut one node, the other nodes stdout notifications about that node