You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been implemented ages ago, so why are we this late in adopting this?
For those who are not familiar:
"Chaos Monkey randomly terminates virtual machine instances and containers that run inside of your production environment. Exposing engineers to failures more frequently incentivizes them to build resilient services."
So please everyone, we need to drop everything and make sure we adopt a Chaos Engineering mindset!
The text was updated successfully, but these errors were encountered:
I don't feel comfortable with the current state of the product. It seems not reliable enough.
I saw that there are a lot of issues about making this a bit more not-so-ancient and move to Kubernetes:
#363 comes to mind.
which would solve all our problems (future ones also)!!11
Using https://github.com/chaos-mesh/chaos-mesh we can properly test that everything is reliable. After all: "two is one and one is none".
This has been implemented ages ago, so why are we this late in adopting this?
For those who are not familiar:
"Chaos Monkey randomly terminates virtual machine instances and containers that run inside of your production environment. Exposing engineers to failures more frequently incentivizes them to build resilient services."
So please everyone, we need to drop everything and make sure we adopt a Chaos Engineering mindset!
The text was updated successfully, but these errors were encountered: