Mar 16, 2023
When you’re a new startup, identifying the primary use case is essential. At the start, you guess to get into the ballpark. And you iterate and refine based on customer feedback.
When we began Skyramp, we knew we wanted to help cloud native app developers become more efficient. We hypothesized that developer efficiency took a hit each time code came back from later on in the CI CD pipeline for debugging. We called this the “reactive” use case — if we offered an easier, faster way for developers to test APIs and microservices and get back to building at this particular moment we’d have our best shot at getting known and getting used.
And then a wonderful thing would happen. Skyramp is all about reusability, so once developer #1 solved for the first reactive case, when the same thing happened to developer #2, some of the work would already be done, making Skyramp even easier and faster to use. Eventually, tests covering more and more of the app would be explorable via Skyramp. The team would have the freedom to focus on any part of their cloud native app and ensure functional and load-based performance. But now, they could do it proactively — checking for potential errors earlier in the software design process. No additional labor required. We called this the proactive case. It’s part of our vision for shift left microservices testing.
Will it work? We’re going to find out.