piker
piker copied to clipboard
Document the many distributed "modes"
The runtime has been built to handle distributed, many host, deployments from the ground up; there are quite a few configurations for this (and many more to come B)
Let's start listing the possible ploys..
-
[ ] full
pikerdactor tree runs on local host but (ib) API gateway is on remote host and (maybe) the tsdb is running on a remote (indocker). -
[ ]
pikerdruns on local host- +remote
brokerd+samplerd - +remote
emsd - +remote fsp cluster
- +remote
-
[ ]
pikerdruns remote but "some" of it's subactors are spawned locally:-
brokerdis local - rest of tree is in
pikerdtree
-
.. more to come
Doc all the configs
- [ ]
$HOME/.config/piker/conf.toml-
[network]section for laying out bind and connect sockaddrs - some some drafted out ideas in another file somewhere..
-