-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
How would you seed a new subsystem with historical data ?
Example usecase:
Subsys Xhas an egress-esg that emits external events and store them to its event lake- we create
Subsys Yand a routing rule to send external events sent by other subsytems to its event bus. - but Subsys Y also needs historical data
Possible solution:
a script similar to the aws-lambda-stream-cli that reads from Subsys X's event lake and sends the events to Subsys Y's event bus. It could work but I fear that it would send duplicates to Subsys Y's event lake.
Has anyone faced this problem before?
Metadata
Metadata
Assignees
Labels
No labels