Passionate about everything related to computer science. Working as devops engineer and studying ML and blockchain. Currently working on https://github.com/Noovolari/leapp
Thanks a lot! Really happy you find it useful and really excited I brought chaos engineering to your attention! Well, I’ll start with the famous line “everything fails all the time” from Werner Vogels. Since in distributed systems you are certain that someplace, somewhere, something will break, software engineers take that to the extreme as purposely introducing disruption inside their services. Chaos engineering does just that, it’s a practice to purposely introduce disruption to test your services (I think the most famous one was the Chaos Monkey) in different aspects: networking, storage, failing services, etc. It’s an incredibly interesting practice if you want to go deep :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks a lot! Really happy you find it useful and really excited I brought chaos engineering to your attention! Well, I’ll start with the famous line “everything fails all the time” from Werner Vogels. Since in distributed systems you are certain that someplace, somewhere, something will break, software engineers take that to the extreme as purposely introducing disruption inside their services. Chaos engineering does just that, it’s a practice to purposely introduce disruption to test your services (I think the most famous one was the Chaos Monkey) in different aspects: networking, storage, failing services, etc. It’s an incredibly interesting practice if you want to go deep :D