daviddoji
/
professional-programming
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add outage response

This commit is contained in:
Charles-Axel Dein 2016-03-14 14:25:47 +01:00
parent a2c82882ad
commit 75ab44b47d
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -7,6 +7,7 @@
- [Must-read articles](#must-read-articles)
- [Things to do](#things-to-do)
- [Coding](#coding)
- [Incident response (outages, firefighting)](#incident-response-outages-firefighting)
- [Managing the database](#managing-the-database)
- [Releasing & deploying](#releasing-&-deploying)
- [Testing](#testing)
@ -55,6 +56,11 @@ I've found these books incredibly inspiring:
* [Write code that is easy to delete, not easy to extend](http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to)
* [Lessons learned writing highly available code](https://medium.com/imgur-engineering/lessons-learned-writing-highly-available-code-7eaf3d7aae00#.u7c4j6hac)
### Incident response (outages, firefighting)
* [Incident Response at Heroku](https://blog.heroku.com/archives/2014/5/9/incident-response-at-heroku)
* [Blameless PostMortems and a Just Culture](https://codeascraft.com/2012/05/22/blameless-postmortems/)
### Managing the database
* [Safe Operations For High Volume PostgreSQL](https://www.braintreepayments.com/blog/safe-operations-for-high-volume-postgresql/) (this is for PostgreSQL but works great for other db as well).