-
Story
-
Resolution: Done
-
Major
-
None
-
8
-
2020 Week 43-45 (from Okt 19)
Currently Cloud Events logic and backend logic is scattered across all our codebase, with backend-specific logic (kafka, http)
The goal of this task is to come up with a shared design to abstract the concept of Cloud Event from its implementation, to be able to refactor the codebase accordingly.
notes:
- cloud events scattered
- data event interface
- CE SDK 2.0
- trusty AI messages (cloud events ?)
- process -> data index should be CE
- protocols kafka / http
- process.ProcessId.???
CloudEventComponent
- receives message (http/kafka)
- dispatch to other components
- knative addon = http
- trusty = kafka
- data index = kafka
- job service = kafka
- custom service w/ message event
=> smallrye binding in properties = kafka
- SPI import
- abstract message bus
- SmallRye Messaging
- Spring Boot Messaging
1 topic per service in
1 topic per service out
- blocks
-
KOGITO-3250 Rules + Kafka (Research Spike)
- Closed
- is blocked by
-
KOGITO-3407 CloudEvent Kafka Publisher+Emitter (Spring Boot)
- Resolved
-
KOGITO-3408 CloudEvent Kafka Publisher+Emitter (Quarkus)
- Resolved
-
KOGITO-3723 Use trigger name as cloud event type in producer
- Resolved
-
KOGITO-3753 CloudEvents: Update Documentation
- Resolved
-
KOGITO-3409 Shared CloudEvent implementation PoC
- Closed
- is related to
-
KOGITO-3773 Consolidate CloudEvents (part 2)
- Open
- relates to
-
KOGITO-3297 Upgrade CloudEvents dependencies to SDK 2.0.0-milestone2
- Resolved
- links to