Thanks for posting. There's one piece of this that hasn't quite clicked yet for me, which is UI refresh coupled with the event stream approach. In the article's example, for instance, you have the user events going into the stream, which refreshes the cache, db, data warehouse, etc.
In a normal UI, the user makes some action, which would update the db, clear the cache for the affected key(s), and display the updated page to the user. In the event stream processing way, if the front end events are what is being logged and the cache refresh for example is running via Samza or some other processor, how does the UI get refreshed appropriately since the processing of the stream is decoupled? Or does the main app cache remain coupled to the form submission and there are just 'other' uncoupled caches, etc?
In a normal UI, the user makes some action, which would update the db, clear the cache for the affected key(s), and display the updated page to the user. In the event stream processing way, if the front end events are what is being logged and the cache refresh for example is running via Samza or some other processor, how does the UI get refreshed appropriately since the processing of the stream is decoupled? Or does the main app cache remain coupled to the form submission and there are just 'other' uncoupled caches, etc?