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.
Kevin Beck is a senior software engineer at New Relic working on the team responsible for data ingest and all things Kafka. Previously, Kevin spent 15 years at IBM and Informix, working on distributed relational databases.
For exhibition and sponsorship opportunities, email velocity@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of Velocity contacts
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • confreg@oreilly.com