Simulate prod in your K8S dev environments

How it works

Speedscale’s AI trains on your API traffic in Kubernetes environments via sidecars and redacts PII. You can also use Postman collections or logs.

Traffic can be simulated as inbound invocations or backend mock responses. Auth tokens, dates, and other data patterns are analyzed and parameterized in order to be replaced so your systems think it’s in a fully-integrated end-to-end environment.

Once we know the traffic, developers can augment the traffic with various data permutations to increase the amount of scenarios run.

API Observability

Since Speedscale observes traffic, this data can be leveraged to debug new releases, perform root-cause analysis in staging environments and understand runtime API behavior. PII and sensitive data redaction included.

Real-time replacement of key fields and dates

Speedscale can automatically detect and mock your dependencies.
Service mocks are simulators that accept outbound requests from your app and mimic responses coming back from 3rd parties.

Speedscale mocks contain PII-redacted, sanitized traffic so you don’t need to worry about sensitive data being used.

				
					"chaos": {
     "chaosPercent":25,
     "badStatusCodes": true,
     "intermittentResponses": true,
     "randomLatency": true,
     "randomHighLatencyMs": 5000
     }

Performance, regression and
chaos test without multiple tools

Traffic replay pods are ran locally in your clusters by a Kubernetes operator for traffic replay.

Test results are logged and sent to Speedscale for analysis and reporting. Pods are cleaned up afterward to return the cluster to the original state.

How Does Traffic Replay Work?

Observe

Speedscale can ingest traffic through a variety of means such as sidecar, Postman collections, and schemas. Data is gathered in your cloud and sanitized for security, so no sensitive data ever leaves.

Analyze

Speedscale then intelligently parameterizes key fields such as timestamps, unique IDs, and customer/order IDs in order to replace them with realtime values during traffic replay for flexible reuse. Tokenization can be customized. Collected traffic can be browsed, filtered and selected in the Traffic Viewer to auto-generate tests and mocks from.

Replay

To replay traffic, you create “Snapshots”. A Snapshot is essentially a test suite that can contain either a traffic Generator pod, Mock pod or both. Upon replay, the appropriate pods are spun up by our Operator to run the simulation and validations. Traffic for Snapshots can be multiplied, sped up or slowed down. Responses from the Mock pod can also be configured for 404’s, latency, and network black holes.

Installation Options

Speedscale’s Operator and Sidecars for listening can be installed via Helm, CRD, or annotations. We also have a CLI *speedctl* that can be installed and used to automate many install, record, and replay tasks.