And It All Went Horribly Wrong: Debugging Production ... - Joyent

15.11.2014 • Views

Share Embed Flag

And It All Went Horribly Wrong: Debugging Production ... - Joyent

And It All Went Horribly Wrong: Debugging Production ... - Joyent

DOWNLOAD ePAPER

qconsf.com

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

START NOW

In the beginning...<br />

Thursday, November 17, 2011

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

2008, Davisworld.org DSLs in Groovy Say what you mean ... - QCon

amazon s3 - QCon

Download slides - QCon

Download slides - QCon

Download slides - QCon

How to do 100K+ TPS at less than 1ms latency

An Overview of Guava: Google Core Libraries for Java

In the beginning... Thursday, November 17, 2011

In the beginning... Sir Maurice Wilkes, 1913 - 2010 Thursday, November 17, 2011

Page 1: And It All Went Horribly Wrong: Deb
Page 5 and 6: Debugging through the ages • As s
Page 7 and 8: Do we still need to care about fail
Page 9 and 10: Wait, it gets worse • This assume
Page 11 and 12: Debugging in the modern era • Fai
Page 13 and 14: Postmortem advantages • There is
Page 15 and 16: Postmortem challenges • Must have
Page 17 and 18: Postmortem debugging • Postmortem
Page 19 and 20: Postmortem debugging: node.js • D
Page 21 and 22: Debugging transient component failu
Page 23 and 24: DTrace • Facility for dynamic ins
Page 25 and 26: DTrace for node.js • Given the na
Page 27 and 28: Extending DTrace into the VMs • T
Page 29: Thank you! • Dave Pacheco (@dapsa