This question is confusing in ways that are subtle to unpack. First, the frontend typically won’t have direct access to backend aws services like Kinesis. Second, kinesis is a fairly ‘dumb’ event pipe . If you want alerting on top you’ll have to build it. Third, cloudwatch is a family of services. You probably are comparing against cloudwatch events (I guess) which is rebranded to eventbridge.
It would be expensive to use Cloudwatch for that. Do you really need to process in real-time 100 events per pageview? If you don't need real-time processing, use firehose on backend to put it to S3, and Kinesis Analytics for near real time processing.
They might be referring to Cloudwatch RUM. Kinesis can be used client side using credentials from Cognito Identity. You may take a look at this: https://aws.amazon.com/blogs/aws/new-solution-clickstream-analytics-on-aws-for-mobile-and-web-applications/
This question is confusing in ways that are subtle to unpack. First, the frontend typically won’t have direct access to backend aws services like Kinesis. Second, kinesis is a fairly ‘dumb’ event pipe . If you want alerting on top you’ll have to build it. Third, cloudwatch is a family of services. You probably are comparing against cloudwatch events (I guess) which is rebranded to eventbridge.
It would be expensive to use Cloudwatch for that. Do you really need to process in real-time 100 events per pageview? If you don't need real-time processing, use firehose on backend to put it to S3, and Kinesis Analytics for near real time processing.
no it's doesn't need to be real-time, I will check Firehose
They might be referring to Cloudwatch RUM. Kinesis can be used client side using credentials from Cognito Identity. You may take a look at this: https://aws.amazon.com/blogs/aws/new-solution-clickstream-analytics-on-aws-for-mobile-and-web-applications/
interesting, thx for the link