Our Evolution to GraphQL: Unifying our API Strategy
Download as PPTX, PDF0 likes157 views
New Relic adopted GraphQL to address issues from rapid growth including an unwieldy code base, difficulty managing changes, and engineering stress. GraphQL provided a common API language and extensible layer to divide code into microservices and containers while simplifying authorization and allowing client-driven querying and updating across multiple services.
1 of 5
Download to read offline
More Related Content
What's hot (19)
Ad
Similar to Our Evolution to GraphQL: Unifying our API Strategy (20)
Ad
More from New Relic (18)
Recently uploaded (20)
Our Evolution to GraphQL: Unifying our API Strategy
- 1. ©2008–18 New Relic, Inc. All rights reserved New Relic's API Journey Using GraphQL Mark Weitzel Sr. Director, Platform & Ecosystem
- 2. ©2008–18 New Relic, Inc. All rights reserved 2 Motivation Expanding technology landscape Expanding product portfolio Expanding code base Rapid Growth Single rails code base Unwieldy & difficult change management Innovation vs. Reliability Engineering Stress
- 3. ©2008–18 New Relic, Inc. All rights reserved 3 Divide and Conquer Containers (Docker) Message Queues (Kafka) Microservices Formalized UI component architecture (React) Common visualization library Componentized UI Elements Simplified Authorization Common API Language Extensible API Layer
- 4. ©2008–18 New Relic, Inc. All rights reserved 4 GraphQL Proxy GraphQL Server (Account) GraphQL Server (Infrastructure) GraphQL Server (NRDB) GraphQL Server (...)
- 5. ©2008–18 New Relic, Inc. All rights reserved SHOWTIME! ©2008–18 New Relic, Inc. All rights reserved Demo 1. Basic GraphQL query 2. Access to multiple services 3. Client driven result sets 4. Updating (mutation) data 5. Other surprises along the way