Skip to content

Commit

Permalink
Update Adopters (AbInbev, CI&T) (litmuschaos#3754)
Browse files Browse the repository at this point in the history
* Create ci&t.md
* Create abinbev.md
* Update ADOPTERS.md
  • Loading branch information
prithvi1307 authored Sep 2, 2022
1 parent 1f901c5 commit 7f1e279
Show file tree
Hide file tree
Showing 3 changed files with 31 additions and 0 deletions.
2 changes: 2 additions & 0 deletions ADOPTERS.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ The companies listed here conform to [CNCF's definition of end-users](https://gi
|[FIS](https://www.fisglobal.com/en/)|Larger SRE Transformation with Chaos Engineering|[Our Story](adopters/organizations/fis.md)|
|[Adidas](https://adidas.com/)|Implementing Chaos Engineering as a practice at Adidas|[Our Story](adopters/organizations/adidas.md)|
|[Cyren](https://www.cyren.com/)|Implementing Chaos Engineering as a practice at Cyren|[Our Story](https://www.infoq.com/articles/chaos-engineering-cloud-native/)|
|[AB-Inbev](https://www.ab-inbev.com/)|Implementing Chaos Engineering as a practice at AB-Inbev|[Our Story](adopters/organizations/abinbev.md)|

### Cloud-Native Vendors

Expand Down Expand Up @@ -54,6 +55,7 @@ They use LitmusChaos as the tool of choice for carrying out chaos experiments in
|[WeScale](https://www.wescale.fr)|[Chaos Engineering](https://blog.wescale.fr/2020/03/19/le-guide-de-chaos-engineering-partie-2/)|[Our Story](adopters/organizations/wescale.md)|
|[Wipro](https://www.wipro.com/en-IN/infrastructure/wipros-appanywhere/?utm_source=github&utm_campaign=litmuschaos_repo)|[Wipro AppAnywhere](https://www.wipro.com/en-IN/infrastructure/wipros-appanywhere/?utm_source=github&utm_campaign=litmuschaos_repo)|[Our Story](adopters/organizations/wipro.md)|
|[HCL Cloud Native Labs](https://www.hcltech.com/)|SRE Enablement Service|[Our Story(TBA)]|
|[CI&T](https://ciandt.com/us/en-us)|Chaos Engineering Implementation|[Our Story](adopters/organizations/ci&t.md)|

### Cloud-Native OSS Projects

Expand Down
15 changes: 15 additions & 0 deletions adopters/organizations/abinbev.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
## AB-Inbev

Anheuser-Busch InBev SA/NV, commonly known as AB InBev, is a Belgian multinational drink and brewing company based in Leuven, Belgium. AB InBev has a global functional management office in New York City, and regional headquarters in São Paulo, London, St. Louis, Mexico City, Bremen, Johannesburg and others.

## Why Do We Use Litmus:

After an evaluation period of some Chaos Engineering tools, we chose Litmus because it is a more mature tool that would meet most of our needs. We are in the implementation, configuration, and process definition phase.
AB-Inbev's BEES is a huge project that has hundreds of microservices, it has been a great challenge to adapt Litmus in this process, making customizations and counting on the help of the Litmus community to evolve the tool and thus achieve our goal of making it available to the teams.
Some points that made us choose Litmus:

- Based on K8S resources
- SSO
- Customization of attacks, attacks in parallel
- Installation on multiple clusters
- GitOps
14 changes: 14 additions & 0 deletions adopters/organizations/ci&t.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## CI&T
CI&T is an information technology and software engineering company. CI&T operates as a global systems integrator headquartered in the Brazilian city of Campinas with offices in other regions of South America, United States, Europe, and Asia.

## Why Do We Use Litmus:

After an evaluation period of some Chaos Engineering tools, we chose Litmus because it is a more mature tool that would meet most of our needs. We are in the implementation, configuration, and process definition phase.
AB-Inbev's BEES is a huge project that has hundreds of microservices, it has been a great challenge to adapt Litmus in this process, making customizations and counting on the help of the Litmus community to evolve the tool and thus achieve our goal of making it available to the teams.
Some points that made us choose Litmus:

- Based on K8S resources
- SSO
- Customization of attacks, attacks in parallel
- Installation on multiple clusters
- GitOps

0 comments on commit 7f1e279

Please sign in to comment.