neo01124

10 ms·

1. 1.▲
   by neo01124 6y ago

   That is more about the "engineering" bit.
2. 2.▲
   by neo01124 6y ago

   The article does talks about how to inject latency or packet-loss into calls to particular external services. This should help you test many service->dependency failure scenarios around retries, timeouts and circuit-breakers. Injecting s
3. 3.▲
   by neo01124 6y ago

   No, there is no different approach. You are misunderstanding what is being addressed in the article. This is not about bare metal vs cloud or autoscaling vs no-autoscaling/overscaling or developer time vs resource costs. The article ta
4. 4.▲
   by neo01124 6y ago

   Stress testing a whole app ecosystem end-end and preventing/mitigating end user impact is generally a part of "gamedays" - https://wa.aws.amazon.com/wat.concept.gameday.en.html . A library like AWSSSMChaosRunn
5. 5.▲
   by neo01124 6y ago

   Author of the article here. Please take a look at the underlying library here (AWSSSMChaosRunner) - https://github.com/amzn/awsssmchaosrunner
6. 6.▲
   by neo01124 6y ago

   Hi! Author of the article here. The core concern is not about the capabilities of the compute abstraction being used (bare metal, containers or functions) or testing OS capabilities. The aim is to validate mitigations which are in place to
7. 7.▲
   by neo01124 6y ago

   Hi! Author of the article here. The AWSSMChaosRunner approach can't be used for Lambda because of what @vasco said. You can take a look at a different approach here for failure injection in Lambda - https://medium.com/