-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal for presentation, week3: An Introduction to Application-level Chaos Engineering and Its Tools #369
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| # Presentation Proposal : "An Introduction to Application-level Chaos Engineering and Its Tools". | ||
|
|
||
| ## Members | ||
| Nagasudeep Vemula, [email protected] | ||
| Github:nagavem | ||
|
|
||
| Akhil Yerrapragada, [email protected] | ||
| Github: akhilyerrapragadaa | ||
|
|
||
| ## Description: | ||
|
|
||
| -Introductions to fault engineering and chaos engineering and a comparison between them. | ||
| -Performace evaluation of a spring application using chaos machine/chaos monkey. | ||
| -A look into the tools that would be used for chaos engineering.We will delve into the different use cases for them and the different categories of tools that are available at the moment. | ||
|
|
||
| -Relevance to Devops: With regards to the relevance, Adding continuous chaos to DevOps culture helps us build better anti-fragile applications. | ||
| -Technical and business metrics to be considered. | ||
| -Chaos Experiments to be run. | ||
| -And finally, Chaos engineering maturity. | ||
|
|
||
|
|
||
| ## References: | ||
|
|
||
| [Chaos Machine Deep Dive](https://doi.org/10.1109/TSE.2019.2954871) | ||
| [Chaos Engineering in Devops] (https://medium.com/capital-one-tech/continuous-chaos-introducing-chaos-engineering-into-devops-practices-75757e1cca6d) | ||
| [Tool Comparison] (https://www.gremlin.com/chaos-engineering/chaos-engineering-tools-comparison/) | ||
| [Chaos Engineering in IT] (https://devops.com/chaos-engineering-for-itops/) | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
incorrect Markdown links here (space between square bracket and parenthesis), could you fix please? you may add bullets also. Thanks!