Nate Lee
Yeah. In fact, I mean, we're using the word testing, but we don't think of our solution as testing at all. We actually think of it as kind of the anti-test. So with most of these testing solutions, the base test is like kind of the core element of the framework. You've got a Selenium or Cypress or Playwright test, or you've got like a Postman or a Jmeter test. That test is the base element. And then you actually copy-paste that test and you create more of them. First, for the way we look at the world, traffic is your base element. You're taking spans of traffic. We call them snapshots. So you're taking snapshots of traffic and actually going through that traffic and saying, do I like this traffic? Is this representative of the day-to-day interactions that we're seeing? Right there immediately, A, it's more realistic, right? Because testing usually is a guess of how I'm going to be encountering my customers. Like so, for example, I don't know if, you know, I'm testing the order of basketballs, but really the thing that sells the most is footballs at my retail store. Well, I could be testing the wrong user flow or the wrong skew. And so there's something to be said for testing realistically or replaying traffic realistically. And then secondly, once you do have an idea of what you want to exercise in your application, you have to go build it. You have to write code to write more code. Usually, there's a scripting language that's associated with these solutions. But if you can just actually look through lengths of traffic and say, hey, this is a good user flow, I want to use this traffic flow, you can actually take that session and then multiply it and then direct that traffic at your environments. The next kind of differentiator as well. And the question that pops up at that point is, well, if I'm replaying traffic, if I don't have the right test data set up or the right skew available, then none of this is going to succeed anyway. And so we've already preempted that by what we do is when we're capturing traffic, we also capture the interactions that are going to the backend systems. And so the way we do this is by using a Kubernetes sidecar where we can work with other containerized environments. But sidecars are very well understood kind of Kubernetes pattern. And so by capturing this traffic, the developer now got a way to self-service kind of go into the solution and understand okay I want to exercise this API. What do I need back-end wise environment wise to exercise this API. And then secondly how do I get it? Conventionally, you may be doing this in your organization by saying, well I need to talk to the lead engineer. I need to talk to the architect, I need to talk to the DBA to get this instance going. And then you got to go set it up in a cluster somewhere or maybe you've already got the cluster. But the problem is everybody in there, brother, is already in that cluster. They're using data. They're running their own performance tests which may conflict with yours. You get the idea. So these are just a few ways we're different. By looking at traffic we can kind of auto generate the traffic that's hitting your app. And we can auto-generate the test environment as well. The idea is we can kind of give you orders of magnitude faster execution.