Systems | Development | Analytics | API | Testing

Ephemeral test environments have surfaced as a solution to DevOps teams’ growing challenges. Dealing with spiraling cloud costs and infrastructure maintenance is only getting more complex. Development teams find themselves competing for limited or stale environments while datasets grow larger. As a result, development velocity suffers. Application teams need realistic data for effective testing.

Since the release of the Defense Innovation Board (DIB)'s Software Acquisition and Practices (SWAP) report in 2019, the Department of Defense (DoD) has focused on adopting and recommending DevSecOps best practices for aerospace and defense development and software acquisition, as detailed in the DoD's 2024 State of DevSecOps report.

Many organizations turn to database subsetting for various reasons. For one, cloning entire terabyte datasets could bankrupt your cloud budget. And masked data could leave your teams fumbling with unrealistic test scenarios. Why wouldn't you just grab the data you need? Sometimes, it really is that straightforward. For certain use cases — like lightweight testing scenarios, proof-of-concepts, or applications with simple data structures — subsetting delivers exactly what it promises.

Developer experience (DX) — the ability for developers to easily do their essential tasks — has become crucial for attracting and retaining talent. Skilled developers are in short supply, but demand for their expertise continues growing. I've seen companies forced to maximize their current workforce while competing globally for talent. I also consistently see companies unknowingly damaging their DX through poor processes in overlooked areas.