> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-12-14-event-reusability.md).
# Day 12/14 Event Reusability
Day 12 of 14: Maximize the business value of your digital assets by leveraging EDA's publish-subscribe pattern to reuse real-time event streams for big data analytics without impacting core performanc
Digital transformations generate a vast array of events, crucial for unlocking innovative use cases. Transitioning these events across the organization breaks down silos, opening doors to unprecedented opportunities.
In a business setting, **events are intricately linked in a process flow to achieve specific functions**. The event process flow allows various services to subscribe to these events for diverse purposes. Event-Driven Architecture (EDA) plays a pivotal role in enabling real-time event gathering from the event mesh without compromising performance or introducing additional logic to the application.
In the realm of EDA, data scientists can leverage the analysis of millions of similar events to craft distinct campaigns. These campaigns could focus on promoting best-selling products, eliminating unwanted items or pages, optimizing system capacity by utilizing timeslot usage statistics, or tailoring personalized promotions based on customer interactions.
A key strength of Event-Driven Architecture lies in its capacity to **repurpose events efficiently, elevating their significance as digital assets** while maintaining optimal performance. To fully capitalize on this capability, meticulous documentation of all events within a centralized repository is imperative, fostering seamless collaboration across teams.
Moving forward, the aim is to enhance the effectiveness of reusing events to maximize their value in supporting both business operations and marketing endeavors. A crucial step towards this goal is establishing a tailored event reuse strategy aligned with the unique nature of your organization's business.
Let's delve into a practical example using a gaming product to demonstrate how event reuse can bolster your business objectives. Visualize a transformation diagram where the central red circle signifies the core operation intertwined with multiple event flows. Initially, the product is defined for sale, setting off a chain reaction of initial odds. Customers then engage by logging into their accounts to place wagers (tickets) on specific products (markets) through diverse channels. The turnover of these designated products influences subsequent odds adjustments, culminating in a cyclical progression.
This iterative cycle, encompassing a myriad of events, leverages event reusability to interconnect discrete events through segregated logic. This recurrent process amalgamates diverse events to furnish valuable insights and feedback for the business via comprehensive big data analytics.
This intricate process thrives on an event-driven, publish-subscribe communication pattern. A key strength of this methodology lies in its seamless integration of new subscribers or data consumers without disrupting existing applications. These additional functionalities operate autonomously, safeguarding the continuity of event flows and application performance. Concurrently, they furnish actionable insights to target specific audience segments, craft more impactful marketing initiatives, and enhance customer engagement effectively.
**Question** Who will be responsible for drafting the event reusability strategy in your organization?
## 🚀 Let's Connect Beyond GitBook!
If you found this article helpful, you can find more of my technical insights, daily discussions, and deep dives across these platforms:
* **Read more of my work:** Check out my articles on [dev.to](https://dev.to/stephen_tsoi_5b2c4055f3a9) and [Hashnode](https://stephentsoi.hashnode.dev/).
* **Join the daily conversation:** Connect with me directly on [LinkedIn](https://www.linkedin.com/in/stephen-tsoi-16309730/).
***
#### 📬 Stay Ahead of the Curve
Enjoyed this piece? I break down complex technical topics into bite-sized, actionable insights every week.
👉 **Subscribe to my** [**LinkedIn Newsletter**](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7487299517642612736) to never miss an update and get the latest articles delivered straight to your feed!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day-12-14-event-reusability.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
