Thriving under a continuous self-inflicted DDoS attack
New Relic customers send monitoring data to New Relic servers every minutea continuous firehose of data. Drawing on his experience at New Relic, Kevin Beck shares best practices for building a streaming service based on Apache Kafka, self-monitoring for reliability and fault tolerance, and building a DevOps culture that anticipates and prevents outages.
| Talk Title | Thriving under a continuous self-inflicted DDoS attack |
| Speakers | Kevin Beck (New Relic) |
| Conference | O’Reilly Velocity Conference |
| Conf Tag | Build resilient systems at scale |
| Location | New York, New York |
| Date | October 2-4, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
New Relic customers embed the company’s agents in their applications to send monitoring data to New Relic servers every minute. The millions of active applications create a continuous firehose of data—which customers expect to be aggregated, persisted, and available for charting and analysis in time for them to do real-time alerting and monitoring. Drawing on his experience, Kevin Beck shares best practices for building a streaming service based on Apache Kafka, self-monitoring for reliability and fault tolerance, and building a DevOps culture that anticipates and prevents outages.
