> 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/general-topic/event-driven-architecture-2.5-years-110+-posts-50+-reposts-with-comment-3+-articles-and-lessons.md).
# π Event-Driven Architecture: 2.5 Years, 110+ Posts,50+ Reposts with comment,3+ Articles and Lessons
A centralized knowledge hub aggregating 2.5 years of technical writing, 110+ posts, and 8 deep-dive articles spanning EDA strategy, MQTT, OpenTelemetry, and governance.
A Practical Knowledge Hub Covering Strategy, Governance, MQTT, Event Mesh, Observability, and Enterprise Integration
Nowadays, enterprisesβ digital systems are increasingly distributed across clouds, datacenters and edge environments, and made up of many purpose-specific microservices instead of a few massive monolithic applications. Event-driven architecture (EDA) is an application design model that enables asynchronous publish/subscribe communication between all of these highly distributed components.
**Event-Driven Architecture (EDA)** has emerged as a key architectural paradigm for enabling asynchronous, scalable, and loosely coupled communication across these highly distributed systems. By leveraging events as the primary mechanism for information exchange, organizations can improve agility, resilience, responsiveness, and real-time business capabilities.
Over the past two and half years, I have been on a personal journey to explore, implement, and share knowledge about Event-Driven Architecture. During this period, I have published more than **110+ posts, 50+ repost with comment and 8 articles**, covering a broad spectrum of topics including:
* EDA strategy and adoption
* Architecture governance
* Event modeling and design
* Event Mesh architecture
* MQTT and messaging patterns
* Observability and distributed tracing
* Real-world implementation experiences
* Best practices and common pitfalls
To make these insights more accessible, I have created this article as a **central EDA Knowledge Hub**, bringing together the content I have shared with the community.
To make these insights easier to access, I would like to use this post as a **central hub** that brings together all of the EDA-related content I have shared with the community.
### π EDA Knowledge Hub
1\. [Event-Driven Architecture: Aligning Technology with Business Outcomes](https://www.linkedin.com/pulse/event-driven-architecture-aligning-technology-business-stephen-tsoi-xwnnc) (8 post):
How EDA can be aligned with business objectives, organizational capabilities, and digital transformation initiatives.
2\. [Building a Hybrid Solution: Integrating REST and MQTT for Secure, High Throughput, Low Latency Communication](https://www.linkedin.com/pulse/stop-choosing-between-rest-messaging-stephen-tsoi-3sa7c) (22 posts)
3\. [Event Governance: The Foundation of Successful Event-Driven Architecture](https://www.linkedin.com/pulse/event-governance-foundation-successful-event-driven-stephen-tsoi-glfvc) (16 post):
Practical approaches to governing event-driven ecosystems, including standards, controls, and operational management.
**4.** [A Missing Event Among Billions? How We Found It on an Event Mesh](https://www.linkedin.com/pulse/missing-event-among-billions-how-we-found-mesh-stephen-tsoi-fynhc) (17 post)
Lessons learned from diagnosing and resolving challenging event-tracing scenarios in large-scale event mesh environments.
**5.** [**From Missing Events to Complete Visibility: Tracing Enterprise Transactions with OpenTelemetry**](https://www.linkedin.com/pulse/from-missing-events-complete-visibility-tracing-enterprise-tsoi-wx0lc) (37 posts):
Explore how OpenTelemetry can provide end-to-end visibility across distributed event-driven systems and help trace transactions across complex enterprise environments.
**6.** [**Event-Driven Architecture: 7 Misconceptions That Architects Still Get Wrong**](https://www.linkedin.com/pulse/event-driven-architecture-7-misconceptions-architects-stephen-tsoi-7vfbc)
A discussion of frequently misunderstood EDA concepts and common assumptions that often lead to implementation challenges.
**7.** [Real-World EDA Use Case](https://www.linkedin.com/pulse/real-world-eda-use-case-stephen-tsoi-eiiic)
Examples of how EDA can be applied across different business domains and technical scenarios.
### π― What You'll Learn
Across these articles and posts, you'll discover practical insights into:
β Enterprise-scale Event-Driven Architecture
β Event Mesh design and deployment
β MQTT and messaging patterns
β Event governance and operational excellence
β Distributed tracing with OpenTelemetry
β Architecture decision-making frameworks
β Real-world implementation challenges and lessons learned
### π€ Let's Learn and Grow Together
If you find these articles useful, please feel free to share them with your colleagues and network. And if your organization is interested in exchanging knowledge, discussing architecture challenges, or sharing EDA success stories, I would be delighted to connect.
\
## π 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/general-topic/event-driven-architecture-2.5-years-110+-posts-50+-reposts-with-comment-3+-articles-and-lessons.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.
