|
282 | 282 | "event_key": "929625",
|
283 | 283 | "active": "Y",
|
284 | 284 | "pinned": "N",
|
285 |
| - "name": "Keynote: How GraphQL is Redefining API Orchestration for the AI Era - Matt DeBergalis, CTO & Co-Founder, Apollo GraphQL", |
| 285 | + "name": "Keynote: How GraphQL is Redefining API Orchestration for the AI Era - Matt DeBergalis, CEO & Co-Founder, Apollo GraphQL", |
286 | 286 | "event_start": "2025-09-08 09:50",
|
287 | 287 | "event_end": "2025-09-08 10:00",
|
288 | 288 | "event_type": "Keynote Sessions",
|
|
624 | 624 | "event_end": "2025-09-08 11:55",
|
625 | 625 | "event_type": "AI / LLMs",
|
626 | 626 | "description": "APIs give AI superpowers. The MCP protocol, introduced less than a year ago, has quickly become a popular method for connecting large language models (LLMs) with the outside world. But where does GraphQL fit in? It's structured, typed, and introspectable... so what's the catch?\n\nJoin our panel of experts as we delve into how to leverage GraphQL effectively and safely in AI applications. We'll discuss the trade-offs, potential pitfalls, and share insights into best practices and strategies. This interactive discussion will explore how combining GraphQL with MCP can unlock new superpowers for AI, offering attendees a chance to engage with thought leaders and gain valuable perspectives.",
|
627 |
| - "goers": "0", |
| 627 | + "goers": "1", |
628 | 628 | "seats": "0",
|
629 | 629 | "invite_only": "N",
|
630 | 630 | "venue": "IJzaal - 5th Floor",
|
|
1303 | 1303 | "event_key": "895837",
|
1304 | 1304 | "active": "Y",
|
1305 | 1305 | "pinned": "N",
|
1306 |
| - "name": "GraphQL Performance Issues at Netflix Scale - Stephen Chambers & Tejas Shikhare, Netflix", |
| 1306 | + "name": "GraphQL Performance Issues at Netflix Scale - Stephen Chambers, Netflix", |
1307 | 1307 | "event_start": "2025-09-08 15:05",
|
1308 | 1308 | "event_end": "2025-09-08 15:35",
|
1309 | 1309 | "event_type": "GraphQL in Production",
|
|
1322 | 1322 | "name": "Stephen Chambers",
|
1323 | 1323 | "company": "Netflix",
|
1324 | 1324 | "custom_order": 0
|
1325 |
| - }, |
1326 |
| - { |
1327 |
| - "username": "tshikhare", |
1328 |
| - "id": "21543712", |
1329 |
| - "name": "Tejas Shikhare", |
1330 |
| - "company": "Netflix", |
1331 |
| - "custom_order": 1 |
1332 | 1325 | }
|
1333 | 1326 | ],
|
1334 | 1327 | "event_start_year": "2025",
|
|
3160 | 3153 | "event_key": "924215",
|
3161 | 3154 | "active": "Y",
|
3162 | 3155 | "pinned": "N",
|
3163 |
| - "name": "Next-Generation GraphQL Cache Management in Your Android and iOS Apps - Benoit Lubek, Apollo Graph & Zach FettersMoore, Apollo GraphQL", |
| 3156 | + "name": "Next-Generation GraphQL Cache Management in Your Android and iOS Apps - Benoit Lubek, Apollo GraphQL", |
3164 | 3157 | "event_start": "2025-09-10 10:20",
|
3165 | 3158 | "event_end": "2025-09-10 10:30",
|
3166 | 3159 | "event_type": "Developer Experience",
|
|
3173 | 3166 | "id": "a0e2a06e7fa0578e1b252beef517aef2",
|
3174 | 3167 | "venue_id": "2152800",
|
3175 | 3168 | "speakers": [
|
3176 |
| - { |
3177 |
| - "username": "zach.fetters", |
3178 |
| - "id": "23098822", |
3179 |
| - "name": "Zach FettersMoore", |
3180 |
| - "company": "Apollo GraphQL", |
3181 |
| - "custom_order": 0 |
3182 |
| - }, |
3183 | 3169 | {
|
3184 | 3170 | "username": "BoD",
|
3185 | 3171 | "id": "431358",
|
3186 | 3172 | "name": "Benoit Lubek",
|
3187 | 3173 | "company": "Apollo Graph",
|
3188 |
| - "custom_order": 1 |
| 3174 | + "custom_order": 0 |
3189 | 3175 | }
|
3190 | 3176 | ],
|
3191 | 3177 | "event_start_year": "2025",
|
|
3348 | 3334 | "event_key": "925047",
|
3349 | 3335 | "active": "Y",
|
3350 | 3336 | "pinned": "N",
|
3351 |
| - "name": "Introducing Pollen - An Open-source Developer Portal Framework for GraphQL - Jason Kuhrt, The Guild", |
| 3337 | + "name": "Imagining the Future of GraphQL Documentation Tooling - Jason Kuhrt, The Guild", |
3352 | 3338 | "event_start": "2025-09-10 11:15",
|
3353 | 3339 | "event_end": "2025-09-10 11:45",
|
3354 | 3340 | "event_type": "Developer Experience",
|
3355 |
| - "description": "There are many aspects to consider when building a GraphQL API: Authentication, authorization, performance, schema design, and team workflow to name a few. Each aspect encompasses considerations, practices, and tools (or lack thereof). One aspect, documentation, can be easily neglected. At The Guild we are building an open source tool called Polen to address this. It aims to make beautiful developer portals easy and reduce the gap of docs tools between GraphQL and REST communities.\n \nThis presentation would mark the first formal introduction of Polen, covering:\n \n1. How/why Polen came to be\n2. What it does so far\n3. What it could do in the future\n \nThis talk would continue the larger docs conversation (e.g. last year https://www.youtube.com/watch?v=kWe_v6YVj8U) by sharing what encoding some of our best docs ideas into tooling could look like. Ideally it would help the audience think about how they can make their APIs more accessible for their users. Finally, given Polen is not a commercial offering, I also hope to inspire people to get involved, make issues, give feedback, and send pull requests.\n \nPolen is already public today at http://github.com/the-guild-org/polen", |
| 3341 | + "description": "There are many aspects to consider when building a GraphQL API: Authentication, authorization, performance, schema design, and team workflow to name a few. Each aspect encompasses considerations, practices, and tools (or lack thereof). One aspect, documentation, can be easily neglected. This year at The Guild I spent time exploring that domain and prototyping an open source tool we’re calling Polen.\n\nI will present our thoughts on what characteristics and features we’d like to have from GraphQL documentation tooling and finish with a demo of how Polen tackled some of those things. I hope this session stimulates your own thinking about what documentation tools should include and tangible technical steps we might take to get there.", |
3356 | 3342 | "goers": "0",
|
3357 | 3343 | "seats": "0",
|
3358 | 3344 | "invite_only": "N",
|
|
0 commit comments