A single instance of the Database Lab Engine (DLE) can generate many fully isolated database clones. These clones can replace the need to setup, maintain, and pay for standalone development and staging databases. Learn how the DLE works.
Most organizations take one of the following approaches to build a staging server:
- Staging has its own data that has been generated internally over time.
- Staging periodically restores a production backup and either
- leaves the data alone violating best practice
- wipes away most of the data leaving only a small percentage
- masks the data using homegrown tools
None of these approaches are ideal because they leave organizations with either suboptimal testing environments or high development and maintenance costs.
The Database Lab Engine (DLE) resolves these limitations by providing instantaneous access to full-size, safely-masked clones of production data.
Test (and even development) environments using clones generated by the DLE make it vastly simpler for software teams to find and resolve bugs before they hit production.
Examples of what teams can do with instantly available production clones:
- Quickly reproduce an issue that surfaced on production without a lengthy setup
- Easily reset a staging or development database while conducting pre-release testing
- Preview precisely how code and data changes will impact production prior to release
A single instance of the Database Lab Engine (DLE) can generate many fully isolated database clones. Allocating new clones is governed by role-based permissions and can easily be done either through our web portal or command-line tool.
With Database Lab, software teams gain access to higher quality data for testing purposes and can reduce the cost of their test environments.