All aspects of event-driven design, streaming technology, and real-time systems essentially revolve around how we see data as events, how we model events and essentially the transition and transformations over the data. The pitfalls often come from thinking a domain itself like a legacy. I would present ten such practices which a team can keep in mind to ensure their event streaming work stays successful and impactful
1. Setting Expectations
2. You Are Not Trying To Build Legacy 2.0
3. Be Aware Of Business Gerunds
4. Don't Overinvest In A Single Platform
5. Upskilling With New Development Paradigms
6. Processing Topology Debugging Can Be Extremely Challenging
7. An Inefficient Topology/Data Pipeline Can Have Lasting Consequences
8. Handling Stateful Workloads
9. Frequently Changing Needs Can Pose Challenges
10. Centralized Ownership Can Be An Existential Threat
The above ten practices would be presented while showing actual examples of what happened while developing and what could have been understood and done better, in a lucid way
(Also based on my recently published article
https://www.forbes.com/sites/forbestechcouncil/2022/05/19/10-best-practices-for-event-streaming-success/)
