> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/install-and-configure-oneweb-platform/plan-your-oneweb-installation/design-oneweb-architecture/production-vs.-disaster-recovery-vs.-testing-environment.md). # Production vs. Disaster Recovery vs. Testing Environment You need to consider the type of environment you need to have when you want to develop an application. First, you can develop your application on your client's machine. Once you have completed the task, it needs to be tested. For that, you should have a Testing Environment. If your application works fine in Testing Environment and you have got the confidence to go live, you need to promote your Application in the Production Environment. If you would like to have continuity of business, you may need Disaster Recovery as a backup plan in case your Production Environment has encountered some problems. This is the most general scenario to develop an application. ### **Production Environment** {% hint style="info" %} Production Environment is the environment or the server where your software applications or products are actually put into operation for their intended uses by end users. This environment is the most important because it affects your business directly. To design the Production Environment, you need to consider the following points. {% endhint %} **Type of your Application** - Is it a real-time application? Is it integrated with other systems? How much data is to be processed? Does it operate 24 hours per day? \ **Type of your Business** - How critical is your business? Who will be affected if this application is down? \ **A number of the user (Active user and Name user)** \ **Number of Transactions** - Number of transactions within a period of time such as the number of transactions in a month. \ **Accepted downtime** - Number of downtimes in a year and how long is the accepted downtime per each occurrence?
### **Disaster Recovery Environment** The Disaster Recovery Environment is the backup environment for your Production Environment and cannot be operated for a long duration. To design the Disaster Recovery Environment, you need to consider the following points. * RPO (Recovery Point Objective) - How much of your data can be lost when you decide to turn on the Disaster Recovery Environment? * RTO (Recovery Time Objective) - How long can it take when you decide to turn on the Disaster Recovery Environment? * How much percent of your Production Environment Capacity do you expect to use in the Disaster Recovery Environment? ### **Testing Environment** Testing Environment is used for testing your application. To design the Testing Environment, you need to consider the following points. * How many testers or people involved do you plan to use the testing environment? * How many systems do you have to integrate with? * How much data do you plan to be used in the testing process? --- # 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://docs.oneweb.tech/oneweb/install-and-configure-oneweb-platform/plan-your-oneweb-installation/design-oneweb-architecture/production-vs.-disaster-recovery-vs.-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.