Building a system that never stops: New Relic at scale
New Relic receives over half a trillion data points from customers that need to be processed, stored, and made available ASAP. Matthew Flaming explains why moving from a single application performance product to querying more than a billion events a second to serve multiple products has meant radically reinventing and re-architecting the whole platform multiple times.
| Talk Title | Building a system that never stops: New Relic at scale |
| Speakers | Matthew Flaming (New Relic) |
| Conference | Velocity |
| Conf Tag | Build resilient systems at scale |
| Location | Santa Clara, California |
| Date | June 21-23, 2016 |
| URL | Talk Page |
| Slides | |
| Video | Talk Video |
In a typical day, New Relic receives over half a trillion data points from our customers. All of these need to be processed, stored, and made available for charts, queries, and alerts as soon as possible. Matthew Flaming explains why moving from the humble roots of a single application performance product to querying more than a billion events a second to serve multiple products has meant radically reinventing and re-architecting the whole platform multiple times. Matthew highlights some of the lessons New Relic learned along the way and offers a glimpse of what’s in store for the future, touching on designing scalable services, optimizing for predictability, measurement, and what it takes to (continuously) rebuild a system that can never stop. This keynote is sponsored by New Relic.
