GraphQL Berlin Meetup #29

New GraphQL Berlin Meetup is coming! Come join us at the stylish Zalando office located opposite to the East Side Gallery.

-------------------------- ❗️README ❗️ --------------------------

Due to Zalando security policy, we require registration. After you fill the form, we’ll send you a confirmation email.

REGISTRATION FORM: https://forms.gle/v1CwSVwGqSr7BkHCA

Please bring along ID with matching name on the day of the event!

If you don't receive confirmation email, it means your name won't be in a list for security, and organizers wouldn't be allowed to let you in.
-------------------------- ❗️end of README ❗️ --------------------------

Meetup schedule
◭ 19:00 - Door open, chit-chat and soft drinks
◭ 19:15 - Welcome & announcements 🤝
◭ 19:20 - “Rethinking GraphQL Batching” by Michael Staib 🎙 + Q&A session
◭ 20:00 - Break
◭ 20:10 - “Death, Taxes, and Deprecation" by Stephen Spalding 🎙 + Q&A session
◭ 20:50 - Networking & pizza 🍕
◭ 21:30 - Door close 👋

---------------------------

🎙 Rethinking GraphQL Batching
🗣️ Michael Staib - ChilliCream
📍 Zürich, Switzerland

While working on the GraphQL composite schema specification, we have explored GraphQL batching and have come up with a variety of new approaches to tackle it. In this talk, I will walk you through why batching is still needed in GraphQL and what problems it solves today. We will also explore some wild experiments with GraphQL batching prototypes that can form business flows to aggregate data, mutate it, and subscribe to updates of the flow with subscriptions. This talk is full of experiments that are to be further explored. So, join me!

---------------------------

🎙 Death, Taxes, and Deprecation
🗣️ Stephen Spalding - Netflix
🔗 http://stephenspalding.com/

When we launched our new GraphQL API at Netflix, it felt perfect—destined to power hundreds of millions of devices. Yet, change is inevitable. Even if your schema seems flawless today (which it isn't), requirements will shift, new features will emerge, and regrets will follow.

GraphQL promises evolvability, allowing us to move forward without multiple API versions. But how does this hold up in practice? We mark fields as @deprecated, but what happens next? How can we embrace experimentation without entombing technical debt in the API? Does federation complicate things? Evolving your schema without breaking clients is easy, right? Right??

Drawing from experience with the Netflix API, this talk explores techniques for evolving your schema safely and painlessly. We'll cover the schema lifecycle—from experimentation to design, deprecation, and deletion.

Attendees will leave with:
- Schema design principles that facilitate change
- Practical techniques for evolving GraphQL schemas
- Strategies for managing a deprecation workflow

Join us as we learn to face the inevitability of change with confidence and serenity.

---------------------------

❗️There are 60/60 seats available. You can be sure you secured a seat, after we send you back a confirmation email.

REGISTRATION FORM: https://forms.gle/v1CwSVwGqSr7BkHCA

please, don't skip README in the beginning of the event description