> 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-1-7-close-to-the-market.md).
# Day 1/7 Close to the market
Day 1 of 7: Learn how combining EDA with Agile and DevOps eliminates point-to-point integration complexity to slash product delivery timelines from months to weeks.
End users often strive for significant transformations within tight budget constraints, aiming for swift launches with minimal risks to meet market demands and enhance customer experiences. Traditional solutions relying on a mix of legacy technologies for point-to-point integration and interconnecting systems through multiple interfaces struggle to effectively achieve these objectives.\
\
**The primary issue lies in the complexity of: 🥑**
* Managing various communication protocols and diverse information types across thousands of interfaces. Even a minor backend data field alteration can impact numerous systems, leading to increased costs, risks, and integration time.
* Addressing network and security compliance, alongside maintaining a sophisticated monitoring solution. Additional logic is required in applications for alerts and data analysis, affecting overall performance.
* Spending considerable time coordinating change impacts with multiple teams, followed by extensive end-to-end testing. Implementing even minor changes can take up to a year due to the thorough testing required.
Event-Driven Architecture (EDA) **seamlessly integrates** with innovative technologies like Agile, DDA, and DevOps to tackle these challenges. By combining EDA with these methodologies, product delivery timelines can be significantly reduced from 8-12 months to just 1-2 weeks, depending on the technology and methodology blend used.\
\
EDA models are crucial in decoupling systems \[], while the Event Portal serves as a robust platform for creating, managing, and regulating various applications, events, and schemas. Embracing Agile practices allows development cycles to be broken into smaller sprints, enabling quick incorporation of necessary modifications. This structured approach follows a 5-step process for implementing changes: Discover, Design, Develop, Test, and Deploy, with iterations possible on a weekly or daily basis.\
## 🚀 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-1-7-close-to-the-market.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.