At ARCCon it was mentioned that the Kinesis events would become less verbose and the expectation would be to leverage the APIs after an event is triggered. I would like to propose this become configurable as there are use cases where this less verbose idea could be detrimental.
For example, frequently an add event will occur and an immediate API get would result in a non-result, the APIs have a cache that delay the availability. When seconds matter, getting all the information from the Kinesis stream can improve the bounds of a third party product.
Additionally for certain events, a 1-to-1 relationship of event and API call could result in a large amount of traffic and load on the API system and also the Kinesis receiver.
Michael Newman
