Chris Richardson
Chris Richardson
# Currently: * If a SagaParticipant sends back a failure message, `step() onReply()` must be used to update the `SagaData` with the error * This can be repetitive if the...
https://github.com/eventuate-tram/eventuate-tram-sagas/blob/e47f49cf7d1e7bdf88d969e98e202d2ad00f85cf/eventuate-tram-sagas-orchestration/src/main/java/io/eventuate/tram/sagas/orchestration/Saga.java#L12
# Current behavior If a local step throws an exception the saga is rolled back. Application code, e.g. `onSagaRolledBack()` does not have access to the exception and so cannot doesn't...
Enhancement of #76
I'm trying: https://docs.flagger.app/tutorials/linkerd-progressive-delivery When I describe the canary deployment - which ultimately failed - I see the following: ``` Warning Synced 28m (x6 over 30m) flagger Error checking metric providers:...
Request/async response is similar to HTTP except that it's message-based: * Client sends an command message to the service * Service sends back a reply message The service owns the...
Unclear why this started to happen with 884c4ba81a205f44b48d74b97c679b7af94996f4: Eventuate CDC connects without issue. ``` 2023-10-15 17:33:29.089 INFO [customer-service,,] 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... 2023-10-15 17:33:31.216 ERROR...
The previous step discovered subdomains. How do those subdomains relate to the bounded contexts? https://github.com/ddd-crew/ddd-starter-modelling-process/blob/dc70a3f35d86246af4e712a06bfd521f486856d6/README.md?plain=1#L307
The section is about 'Connect the sub-domains into a loosely-coupled architecture which fulfills end-to-end business use-cases.' However, the diagram shows bounded contexts, which aren't defined until the next section. https://github.com/ddd-crew/ddd-starter-modelling-process/blob/dc70a3f35d86246af4e712a06bfd521f486856d6/README.md?plain=1#L260