diff --git a/ADOPTERS.md b/ADOPTERS.md index 1f1bda7f1..6ec409b11 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -32,6 +32,7 @@ The companies listed here conform to [CNCF's definition of end-users](https://gi | [Wingie Enuygun Company](https://www.wingie.com/) | Chaos Engineering for an Online Travel and Finance Platform | [Our Story](https://github.com/litmuschaos/litmus/issues/2191#issuecomment-2331265698) | | [EmiratesNBD](https://www.emiratesnbd.com) | Chaos Engineering for Government Owned Bank | [Our Story](adopters/organizations/emirates-nbd.md) | | [PokerBaazi](https://www.pokerbaazi.com/) | Chaos Engineering for Online Gaming | [Our Story](adopters/organizations/pokerbaazi.md) | +| [Amadeus](https://amadeus.com/) | Enhance the resilience and reliability in Amadeus through Chaos Engineering | [Our Story](adopters/organizations/amadeus.md) | ### Cloud-Native Vendors diff --git a/adopters/organizations/amadeus.md b/adopters/organizations/amadeus.md new file mode 100644 index 000000000..03a5f5cda --- /dev/null +++ b/adopters/organizations/amadeus.md @@ -0,0 +1,18 @@ +# Amadeus +[Amadeus](https://amadeus.com/) technology powers the global travel and tourism industry. + +From airlines to search engines, travel agencies to hotels, the world's top travel brands rely on Amadeus to help create exceptional traveler experiences. + +## How do we use Litmus. +We are using Litmus for the following 3 topics: +- **Identify weakness** by injecting a wide variety of disruptions to catch bugs and gaps in the stability of our applications +- **Build confidence in the resiliency** by introducing disruptions that activate our resiliency mechanisms to ensure they are working as expected. +- **Validate fixes** by recreating specific conditions and disruptions, we can reproduce complex production incidents and validate the fixes deployed to resolve them. + +## Benefits in using Litmus. + +We are finding the following benefits in Litmus +- **Open Source**: Allows us to contribute new features and fix bugs based on feedback from our Chaos users. +- **QA-Friendly**: Through the UI and YAML-based configuration, it allows QA profiles with limited SRE knowledge to easily create their own experiments. +- **Extensibility**: As Chaos Scenarios are based on ArgoWorkflow, it allows for the inclusion of custom steps, such as updating a configuration before/after the experiments. +- **Variety of Disruption Types**: Which satisfies our current Chaos users.