> Your k8s pods example is a good source of my hives. Anything that runs on a timer to fire off events is going to get bogged down and lose data I'd have said

> Your k8s pods example is a good source of my hives. Anything that runs on a timer to fire off events is going to get bogged down and lose data I'd have said if you want to gracefully deal with a system that loses events, a timer-based system can ensure the errors from lost events will always be in your customer's favour. The last thing you'd want is to start the taximeter with a start-pod event, then lose the stop-pod event and end up billing the customer for nothing, forever.