version x.y.z
while in beta convention is :
and then
OOP to reduce the repeating of args in function calls
in the tests with carbon clean hierarchy of metrics
implements a simple router
binary star on more than one server orchester
find a way to deploy and package satellites set
astronomy)
ease the multi hosts satellites connection
invent a way to modify the code in the orchester for routing by using
PUB/SUB for rerouting informations simplified coroutines (going the bright side of 10th greenspun law and assumming to borrow the concepts of CLISP)
to use pack and unpack to go full speed and ease the transmission of data coming from C)
I hate humanity (some people wants to watch the world burn)
reduce code, improve reliability, reduce functionnalities to have a better code
re explain some basics of networks/system so that they are aware that their ignorance may cause security issues. Highlight the fact that powerfull tools are a way to shoot yourself a nuclear missile in the knee
of best practices that prevents a DOS by repeated failures of do something at the orchester/tracker level to actively modify routing/ alert when something goes wrong
that are critical and need to be replayed
distributed systems. (can be improved later by using PAIR of REP/REQ for statefull connections that should make it reliable enough if you had a on_happy end hook)
write a tracker that takes full use of the FSM and implement the time_out stuff
in an infinite loop and a processing that takes a lot of time
put a notice on how to design asynch system: bottom half architecture: satellites are bottom halfs.
(yes it is chaotic, but compared to systemd my architecture embrace complexity and the positive property of complex systems such as the resilience to perturbations)
you don’t really need to read the indigests pedantic INRIA papers on vector clock to make a distributed systems works correctly without clock (hint : time is the accident of the accidents)