I would be nice to have more specific event information on the content-operations.
To determine if a content was initially published, saved, republished, etc., multiple fields have to be evaluated.
Processing would be easier if there would be information about the proper action that was made causing the content-operation.
So a field containing clearly specified events would be nice.
Mathias Bauer
this video explains the problem https://www.youtube.com/watch?v=8Af1bh-BVY8
We are using the Kinesis-Stream to react on new stories, republished and unpublished stories.
Case 1 - Updates on the Web-Frontend and Push-Notifications
On our site, users can subscribe to tags, authors and stories.
E.g. if there are new stories for a tag or author, we send out notifications on the Web-App and via Push.
Case 2 - Downstream Systems
We monitor the stories to provide information about new or updated / unpublished stories for inhouse downstream systems
Hi! Thanks for the feedback on the Kinesis Stream. You're absolutely right that there's room for improvement in exposing the actual actions taken in those events. Just for our own benefit, would you mind giving some more details on the workflow(s) your team is using Kinesis for that this would be helpful with?