> 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/real-world-eda-use-case.md).
# 🔀Real-World EDA Use Case
A curated directory of 11 real-world EDA success stories from global leaders like HKJC, Citi, IKEA, and AWS, proving the enterprise viability of event-driven modernizations.
The implementation of Event-Driven Architecture (EDA) presents challenges due to the intricate details of design, implementation, and governance. While the concept is well-understood, there is hesitancy surrounding its practical application, impacting its adoption in the market. Reports from Solace \[Event-Driven Architecture Statistics (2021), [**https://lnkd.in/gDnDTB3U**](https://lnkd.in/gDnDTB3U)] and MuleSoft \[Event-Driven Architecture Report 2024, [**https://lnkd.in/gYzZ87Tj**](https://lnkd.in/gYzZ87Tj)] highlight the discrepancy: over 50% of companies recognize the benefits of EDA, yet only 3% of survey respondents currently utilize it, as indicated in Postman’s "2023 State Of the API Report." Interestingly, messaging technologies like MQTT and AMQP are employed by 18% of respondents, showcasing a different aspect of technological adoption.
Delighted to see the surge in discussions on EDA design and implementation on LinkedIn. Posts like [**Kamran Ali**](https://www.linkedin.com/in/codewithagentsai/)'s "McDonald's Reliable event-driven architecture" ([**https://lnkd.in/gy3Wq\_FM**](https://lnkd.in/gy3Wq_FM)) and [**Igor Iric**](https://www.linkedin.com/in/igor-iric/)'s "Need to build Event-Driven Architecture on Azure?" ([**https://lnkd.in/g2D9PYwx**](https://lnkd.in/g2D9PYwx)) are enriching this conversation. The Annual EDA Summit ([**https://edasummit.com/**](https://edasummit.com/)) provides a vital platform for experts to share their research and organizations to showcase their implementations.
[As](http://implementations.as/) we aim for wider knowledge sharing through diverse channels, I envision fostering virtual connections among domain experts to propel this cutting-edge technology forward. Let us use this post as starting point. I would like to list some valuable showcases from some major organizations as follows. Due to Linkedin size limit, I will add more showcase on the comment.
### Showcases
1. The Hong Kong Jockey Club (HKJC), by [**Chirag Desai**](https://www.linkedin.com/in/chdesai/) and [**Mark Carr**](https://www.linkedin.com/in/mark-carr-998a53/), [**https://lnkd.in/dtnNQ7Tu**](https://lnkd.in/dtnNQ7Tu)
2. RBC by [**Joshua Carroll**](https://www.linkedin.com/in/joshuacarroll101/) , [**https://lnkd.in/gBnFVTTJ**](https://www.youtube.com/watch?v=7kYegz8N0Kc)
3. Chartered Bank (SCB), by [**Sugata Sarkar**](https://www.linkedin.com/in/sugata-sarkar-global-head-technology/) and [**Srinath Sripada Rao**](https://www.linkedin.com/in/srinathsrao/), [**https://lnkd.in/gpMW\_kf5**](https://www.youtube.com/watch?v=Gp7g5EXYj94)
4. Citigroup by [**Gregory Foden**](https://www.linkedin.com/in/gregfoden/) , [**https://lnkd.in/gJgKh74b**](https://www.youtube.com/watch?v=0q3ZLTPO83k)
5. IKEA, by [**Shawn McAllister**](https://www.linkedin.com/in/shawn-mcallister/) and [**Martin Hilferink**](https://www.linkedin.com/in/martinhilferink/), [**https://lnkd.in/griWAh\_C**](https://lnkd.in/griWAh_C)
6. Airtel (Telco), by [**Dr. Sudhir Kumar Mittal**](https://www.linkedin.com/in/dr-sudhir-kumar-mittal-b0775a14/), [**https://lnkd.in/gAvJRdkm**](https://lnkd.in/gAvJRdkm)
7. Nedgia (Gas), by [**Stefano Passaro**](https://www.linkedin.com/in/stefanopassaro/) and [**Alessandro Cagnetti**](https://www.linkedin.com/in/cagnetti/), [**https://lnkd.in/gNwCHHjP**](https://lnkd.in/gNwCHHjP)
8. Revolutionizing Rail, by [**Albertus Indarko Wiyogo CISA, CISSP**](https://www.linkedin.com/in/indarko/), [**https://lnkd.in/g4UxWgj8**](https://lnkd.in/g4UxWgj8)
9. Kinseed Limited (Healthcare), by [**Bob Hundal**](https://www.linkedin.com/in/bob-hundal-35023ab2/), [**https://lnkd.in/gEJxfiNg**](https://lnkd.in/gEJxfiNg)
10. GetGo, by [**Malik Badaruddin**](https://www.linkedin.com/in/malikbadaruddin/), [**https://lnkd.in/gekjA-dN**](https://lnkd.in/gekjA-dN)
11. AWS re:Invent 2022 - Keynote with Dr. Werner Vogels, [**https://www.youtube.com/watch?v=RfvL\_423a-I**](https://www.youtube.com/watch?v=RfvL_423a-I)
The EDA is built on top of product, so please feel free to add other showcase as comment whatever they are using Kafka, Solace, Tibco or other products.
## 🚀 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/real-world-eda-use-case.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.
