> 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-driven-architecture-aligning-technology-with-business-outcomes/day-6-7-promote-reuse-of-system-function.md). # Day 6/7 Promote Reuse of System Function Day 6 of 7: Learn how EDA acts as a self-service platform, allowing Web, Mobile, and ATM channels to reuse 90%+ of backend services consistently without coupling. Many organizations have developed products utilizing different technologies to enhance customer experience. A Web application focuses on providing comprehensive information, while a Mobile client prioritizes user-friendly interactions. Similarly, an ATM may offer efficient shortcuts despite limited information. These products, with distinct UI requirements, share over 90% of data and offer common services like ePayment, ticket sales, and account operations.\ \ In the context of the post "Comparing REST Polling and Event-Driven Architecture: Detailed Design of Event and Service Catalogs" \[] the REST solution requires multiple cache layers for each channel to address performance issues. This setup leads to numerous interfaces with simulated data fields, each catering to a specific channel's page usage. Managing inconsistencies, especially when a single screen needs to call multiple services, adds to the code complexity. The development team continually creates new services based on UI demands.\ \ **Event-Driven Architecture (EDA)** introduces a self-service platform removing dependencies between channels and the backend system. The backend system exposes services directly to the event catalog, breaking them down to the event level. Channel sites can create small functions to subscribe to these events and display them on the UI, ensuring data consistency across various channels.\ \ For instance, in ticket selling, when a customer places a bet on any channel, that channel triggers a Place Bet event on the self-service platform. The backend service subscribes to these events using a persistent queue for processing. Successful bet placement triggers an odds change, disseminating the new odds seamlessly to various channels through the self-service platform.\ \ **This approach allows channel developers to focus on enhancing UI presentations.**
## 🚀 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-driven-architecture-aligning-technology-with-business-outcomes/day-6-7-promote-reuse-of-system-function.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.