Join Zoom Meeting
https://apollographql.zoom.us/j/92527378180?pwd=GXNdFivZ8KhCsk4voTHvWtGVOZ2xeC.1

Join and take notes
https://apollographql.zoom.us/j/92527378180?pwd=GXNdFivZ8KhCsk4voTHvWtGVOZ2xeC.1&mynotes=on

Meeting chat link
https://apollographql.zoom.us/launch/jc/92527378180

Meeting ID: 925 2737 8180
Passcode: 12490500

One tap mobile
+13092053325,,92527378180# US
+13126266799,,92527378180# US (Chicago)

Dial by your location
• +1 309 205 3325 US
• +1 312 626 6799 US (Chicago)
• +1 646 558 8656 US (New York)
• +1 646 931 3860 US
• +1 301 715 8592 US (Washington DC)
• +1 305 224 1968 US
• +1 507 473 4847 US
• +1 564 217 2000 US
• +1 669 444 9171 US
• +1 669 900 9128 US (San Jose)
• +1 689 278 1000 US
• +1 719 359 4580 US
• +1 253 205 0468 US
• +1 253 215 8782 US (Tacoma)
• +1 346 248 7799 US (Houston)
• +1 360 209 5623 US
• +1 386 347 5053 US

Meeting ID: 925 2737 8180

Find your local number: https://apollographql.zoom.us/u/afpGxcd2C

Join by SIP
• 92527378180@zoomcrc.com

GraphQL End to End: Your First Query in 20 minutes

Eeshan Sawant, Ayush More

In this session we will walk you through GraphQL from the very beginning. No prior knowledge needed. We will cover what GraphQL is, how it solves real problems that REST APIs struggle with, and how to write your first query. We will also do a live demo so you can see it working in real time, and not only on slides.

By the end of this session you will understand what GraphQL is, why developers and companies use it, and how to start exploring it yourself.

Scaling GraphQL in Production: N+1, Latency, and Java Virtual Threads

Hasnain Ahmed Shaikh

Moving from REST to GraphQL can provide a more flexible API experience, but operating GraphQL at scale introduces its own set of performance and architectural challenges.

In this talk, we’ll explore practical lessons from building and scaling GraphQL-based customer experiences across multiple marketplaces and languages. We’ll examine how N+1 query patterns can create unexpected latency spikes, how P90 and P99 metrics reveal performance issues that averages can hide, and how resolver and API design choices affect real-world performance.

We’ll then look at Java virtual threads and how they can improve concurrency for I/O-heavy workloads, while also discussing why concurrency improvements alone cannot solve inefficient query patterns or poor GraphQL architecture.

The goal is to provide practical guidance for engineers moving from REST to GraphQL and designing GraphQL services that can perform reliably at production scale.