| 22 Jun 2021 |
tomberek | So events are considered independent? | 22:28:11 |
David Arnold | But it's basically pure event sourcing between brokers, which is a handy byproduct of the message queue used (don't know which) | 22:28:19 |
David Arnold | No, I guess events are considered unique (at most once, at least once semantics) | 22:29:00 |
David Arnold | Not sure though. | 22:29:09 |
David Arnold | Zeebe:
- apiserver + broker
- message queue
- elasticsearch (datalake)
| 22:30:23 |
David Arnold | That's about it. | 22:30:34 |
David Arnold | Ok the broker has fancy features such as distributed runtime state and the workflow engine 😀 | 22:31:08 |
David Arnold | Each bpmn action has roughly/conceptually two events/messages:
JobStart + JobFinish | 22:33:29 |
David Arnold | And workers need to understand those and return meaningful output (JobFinish message) | 22:34:11 |
David Arnold | It's actually pretty simple. | 22:36:05 |
David Arnold | The biggest challange is packaging zeebe / OPA for nixpkgs. | 22:36:33 |
| 23 Jun 2021 |
Taneb | How do the "Previous Hydra evaluation" and "Previous Hydra buld" input types work? | 15:21:59 |