Edge vs. level triggered logic in Kubernetes
speakerdeck.com
Edge vs. level triggered logic in Kubernetes
1–2 of 2 posts
Re: Edge vs. level triggered logic in Kubernetes
#2I find this interesting to use even with common web applications as a design pattern. It's usually easy to just dispatch events but parsing them is always complicated and if you need to do that in all clients youre essentially decoupling the logic. If you can provide already parsed state you are providing the view into that data.