Gremlin and Azure SQL Database

Test how your application handles an Azure SQL Database outage. Run Gremlin network experiments and reliability tests to validate timeouts and failover.

Why SQL Database reliability is important

Azure SQL Database enforces resource limits, and reaching them does not produce a clean outage. It produces throttling, rejected connections, and query timeouts arriving intermittently while the database stays technically available. Applications handle a hard failure far better than they handle this.

The ambiguity is what spreads the damage:

  1. One expensive query pushes the database toward its DTU or vCore ceiling.
  2. Other requests slow down or get rejected, and your application cannot tell a throttled request from a failed one.
  3. Retry logic fires on work that should have been abandoned, adding load to a database already at its limit.
  4. Because the database is shared, teams who never wrote that query start seeing symptoms in their own services.

Gremlin lets you reproduce the messy middle rather than only the extremes. Latency experiments slow the connection to what a throttled client experiences. Blackhole experiments remove the endpoint so you can confirm your connection pool recovers without a restart.

Shared databases spread their problems to teams who did nothing to cause them. Testing shows you how far those problems travel before anyone notices.

Building resilience on SQL Database with Gremlin

SQL Database is a dependency: a managed service that your service connects to. You can run tests by deploying the Gremlin agent or Failure Flags sidecar to a service that consumes SQL Database*. Using the experiments shown to the right, you can prepare your service for SQL Database failure modes, including:

  • Network outages making SQL Database unavailable
  • Slow performance due to network latency
  • Expiring TLS certificates
You can also run these expert-built workflows designed to replicate real-world failure modes on SQL Database:

* Testing a dependency doesn't require installing anything on it. Gremlin runs the experiment from the service that calls it, so compatibility depends on that host rather than on the dependency itself. Check our compatibility documentation for supported operating systems and platforms, or get in touch if you don't see yours.

resources

Learn more about Gremlin and SQL Database

All product names, logos, and brands are property of their respective owners. AWS is a trademark of Amazon.com, Inc.; Azure is a trademark of Microsoft Corporation; Google Cloud is a trademark of Google LLC. Use of these names is for identification purposes only and does not imply endorsement or affiliation unless otherwise stated.

Avoid downtime. Use Gremlin to turn failure into resilience.

Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.

Product Hero ImageShape