> 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-4-7-optimize-the-testing-environment.md).
# Day 4/7 Optimize the Testing Environment
Day 4 of 7: Learn how consolidating disjointed test environments into a production-like non-prod Event Mesh slashes infrastructure costs and accelerates CI/CD automation.
**How Event-Driven Architecture is Designed to Optimize the Testing Environment**\
\
Event-Driven Architecture (EDA) offers a strategic approach to optimizing the testing environment within large organizations. Traditionally, multiple non-production environments serve distinct testing purposes, such as functional tests in the development environment, integration tests in the SIT environment, end-to-end functionality tests in the UAT environment, and load tests in the SAT environment. Given the concurrent nature of numerous projects, the need for multiple instances of these environments arises.\
\
In an EDA setup, a production-like event mesh infrastructure can be established to streamline all non-production environments. This setup provides the flexibility to distribute resources across different environments, enabling developers to conduct high availability (HA), disaster recovery (DR), and load tests on any environment, rather than being confined to SAT alone. By facilitating event routing among different environments, developers can assess application behaviors across various application versions.\
\
Moreover, this infrastructure supports ReadyAPI for automated unit testing, utilizes JMeter to simulate client traffic, and integrates with CI/CD for seamless auto deployments. Leveraging this integrated toolset, organizations can efficiently manage all non-production environment requirements using a single suite of tools.\
\
This consolidated approach **not only reduces costs related to hardware and software licenses but also expedites implementation and testing processes**. Ultimately, the business stands to benefit from enhanced agility, reduced expenses, and minimized risks, aligning closely with market demands and fostering operational efficiency.\
## 🚀 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-4-7-optimize-the-testing-environment.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.
