forked from litmuschaos/litmus
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create infracloud.md * Update infracloud.md * Create apisix.md * Update ADOPTERS.md Signed-off-by: SohamRatnaparkhi <[email protected]>
- Loading branch information
1 parent
5c8666a
commit b4db124
Showing
3 changed files
with
42 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# APISIX Apache | ||
|
||
Developed and donated by API7.ai, Apache APISIX is an open source, dynamic, scalable, and high-performance cloud native API gateway for all your APIs and microservices. It is a top-level project of the Apache Software Foundation. | ||
|
||
You can use APISIX API Gateway as a traffic entrance to process all business data. It offers features including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, and more. | ||
|
||
|
||
|
||
|
||
## How do we use Litmus | ||
We practice chaos engineering using Litmus in the Apache APISIX Ingress. | ||
|
||
Litmus also helped us find hidden bugs. | ||
|
||
Project website: https://apisix.apache.org/ | ||
This is the text version of my online sharing content. https://dev.to/apisix/building-a-more-robust-apache-apisix-ingress-controller-with-litmus-chaos-3ldn |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Infracloud Technologies | ||
|
||
InfraCloud Technologies is a Kubernetes focused B2B Open Source Cloud Native Computing company which has been building products, services, and solutions to modernize applications and infrastructure. | ||
|
||
InfraCloud was one of the first Kubernetes partners and have been contributing to the open source community around cloud-native technologies. It has been growing almost 100% for last few years consistently. | ||
|
||
Company website: https://www.infracloud.io/ | ||
Company GitHub: https://github.com/infracloudio | ||
|
||
## Why Do We Use Litmus: | ||
|
||
At InfraCloud, we are using Litmus to develop Resiliency Frameworks. | ||
To simulate various Chaos scenarios using fault injection templates provided by Litmus. Litmus also helps to incorporate custom fault templates developed using AWS SSM documents. | ||
|
||
## How do we use Litmus. | ||
Currently, we have tested with different kind of scenarios including faults like pod deletion, network latency, resource stressing, network partitioning in databases, and many more. | ||
|
||
## Benefits in using Litmus. | ||
|
||
Easy deployment. | ||
Easy Fault injection. | ||
Custom Grading for experiments | ||
SSM integration helps to inject fault in both EKS and external AWS components. |