Signadot Blog
-
Ephemeral EnvironmentsLeveraging Service Mesh for Dynamic Traffic Routing in Shared Kubernetes Environments
How a tenantID header and dynamic routing in Istio or Linkerd let developers test their own service versions in one shared staging cluster, and two ways to map tenantIDs to workloads.
-
Ephemeral EnvironmentsThe Pitfalls of Using Feature Flagging for Testing in Shared Staging Environments
Why feature flagging falls short for testing in shared staging, from slow feedback and code pollution to refactors and resource leaks, and how isolated ephemeral environments avoid it.
-
Ephemeral EnvironmentsKubernetes Namespace vs Cluster: Pros and Cons for Test Environments
Namespaces, separate clusters and vCluster compared as Kubernetes test environments: where namespaces work, where they break as teams grow, and why teams move to routing on a shared baseline.
-
Ephemeral EnvironmentsTransforming Kubernetes Developer Environments: Duplicate Only What Changed
Why per-developer namespaces and clusters in Kubernetes grow costly and slow as services multiply, how routing requests against a shared baseline isolates changes, and when namespaces still fit.
-
Integration/E2E TestingMocking and Testing 3rd-party APIs with Sandboxes
Why third-party APIs are hard to test against, how the API mocking frameworks MockServer, WireMock, Mockoon and Mountebank compare, and how sandboxes switch tests between mocks and real APIs.
-
Tutorials/GuidesWhat’s the Difference Between an API Gateway and a Service Mesh?
A service mesh handles traffic between services in a Kubernetes cluster, and an API gateway is the entry point for external clients. How they differ, and how the Gateway API standardizes both.
-
Ephemeral EnvironmentsCase StudiesHow Uber & DoorDash empower developers to preview every code change in production
How Uber built SLATE to test changes in production on short-lived environments, and how DoorDash moved from port forwarding to Signadot, both routing requests by header to isolate developers.
-
Case StudiesEphemeral EnvironmentsHow ShareChat Tests Every Pull Request on Kubernetes using Signadot
How ShareChat, with over 500 engineers and more than 100 microservices, tests every pull request in its own sandbox on shared Kubernetes staging and ships features 2-3x faster.
-
Ephemeral EnvironmentsKubernetes Development Environments: Local, Remote, and Production-Like Options
Local clusters like kind and minikube, live-reload tools like Tilt and Skaffold, remote clusters and a shared baseline, compared as setups for Kubernetes development, and how to choose.
-
Case StudiesEphemeral EnvironmentsExploring Kubernetes Testing Evolution: Deep-Dive Case Studies from Eventbrite and Prezi
How Eventbrite and Prezi moved developer testing onto Kubernetes, from Eventbrite's yak tool and 700-node cluster to Prezi's three phases, and the questions that decide which model fits.
-
Integration/E2E TestingUsing Signadot Sandboxes for API Testing
A tutorial that sets up Signadot sandboxes, changes an existing API, and tests it through a sandbox preview URL and Postman while every other service in the cluster stays shared.
-
Is Serverless *Really* For Everyone?
Where serverless fits after Prime Video's move away from it: cold starts with large data loads, why serverless is more than functions, and why the slow development loop hurts most.
No matching posts found.
Stay in the loop
Get the latest updates from Signadot