New approach to manage CI/CD components: Choreography vs Orchestration.
Orchestration = rigid, with single point of failure
choreography paradigm = we have a pool of "resources", each resource has inputs out and outputs, and watches for specific outputs of other resources, which leads to a more composable, scalable approach to CI/CD.
Of course we need tooling to manage this, at a talk at KubeCon (linked below) the presenter talked about Cartographer, it looked cool.
New approach to manage CI/CD components: Choreography vs Orchestration.
Orchestration = rigid, with single point of failure choreography paradigm = we have a pool of "resources", each resource has inputs out and outputs, and watches for specific outputs of other resources, which leads to a more composable, scalable approach to CI/CD.
Of course we need tooling to manage this, at a talk at KubeCon (linked below) the presenter talked about Cartographer, it looked cool.
https://www.youtube.com/watch?v=m0FjctG5uxU https://cartographer.sh/
┆Card is synchronized with this Github issue by Unito