Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Verify System Unavailability Status when Microsoft SQL Server Database Can't Be Reached

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Kubernetes deployments

Download now

Verify System Unavailability Status when Microsoft SQL Server Database Can't Be Reached

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Kubernetes deployments

Download now

Verify System Unavailability Status when Microsoft SQL Server Database Can't Be Reached

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Kubernetes deployments

Download now

Verify System Unavailability Status when Microsoft SQL Server Database Can't Be Reached

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.
Targets:

Containers

Kubernetes deployments

Download now
Go back to list
The experiment editor showing the visual structure of the experiment.The experiment editor showing the visual structure of the experiment.

Intent

An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately

Motivation

Depending on your context, an unavailable Microsoft SQL Server database may be considered so severe that there are no suitable fallbacks. In this case, ensuring that your system is indicating an appropriate error message is essential. After the Microsoft SQL Server database is back again, your system should recover automatically.

Structure

We ensure that a load-balanced user-facing endpoint fully works while having all pods ready. As soon as we simulate an unavailable Microsoft SQL Server database, we expect the user-facing endpoint to indicate unavailability by responding with a "Service unavailable" status. To simulate the unavailability, we can blackhole the Microsoft SQL Server database client connection using the hostname db.internal.steadybit.com so that no incoming or outgoing traffic is going through. The endpoint should recover automatically once the Microsoft SQL Server database is reachable again.


Download now

.json (4 kB)

It's quick and easy

  1. 1.

    Download .json file
  2. 2.

    Upload it inside Steadybit
  3. 3.

    Start your experiment!
Screenshot showing the Steadybit UI elements to import the experiment.json file into the Steadybit platform.
Tags
Microsoft SQL Server
Recoverability
GitHub
steadybit/reliability-hub-db/tree/main/recipes/db-mssql.mssql-unavailable
License
MIT
MaintainerSteadybit

Used Actions

See all
Block Traffic

Blocks network traffic (incoming and outgoing).

Attack

Attack

Containers

Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsExtensionsRecipes
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon