Events remain a useful technical mechanism to transmit state and data among application resources but they are a miserable experience for developers and operato

Events remain a useful technical mechanism to transmit state and data among application resources but they are a miserable experience for developers and operators alike. Events: - Put application state and data in dozens of queues that make the application prone to failures, race conditions and incorrect results - Force developers to think and program asynchronously which is more complex and time consuming than synchronous code - Require developers know more than just their portion of the code and application domain: they also need to understand how to work with queues, caches and event schemas - Make applications difficult to troubleshoot as there is no one place to understand the state and data for an application I say this as someone genuinely interested in this pattern, and in software solutions like Skip: "events" aren't responsible for any of these problems; technical leads producing questionable system designs are. On their own, additional dependencies won't solve problems inherent in the skills/experience/makeup of your team. Open source is great, but projects come and go, and newer ones come with more risk. --- Side note: the only content on the homepage is a button that says "Skip Overview", which is very funny.