The proposed solution for monitoring changes to Inventory records to determine whether updates to the INN-Reach central server are required is to utilize the Kafka queues implemented to support Elasticsearch and remote storage. We need to verify that this is still a viable solution. All we need to know is what transaction attributes are passed in the Kafka message and whether the queue will accept consumers outside the Elasticsearch inventory module and the remote storage modules.
- document structure and example of domain events from Kafka (Mikhail Fokanov & Bohdan Suprun as contact points as well as Viachaslau Khandramai (Firebird team lead)),
- (optional) which event types correlate to which Inn Reach API endpoints (mapping between them).
Time box: 2-3 days