September Meetup

London GraphQL

Sep

7

Thursday, September 7th

from 4:30PM to 6:30PM UTC

In-Person

Address available to attendees

Online

Link available to attendees

We missed you this time around!

This event will be held at Neo4j offices.

Containing topics around, Grafbase, Hasura, Neo4j, and Open Telemetry.

Will be live-streamed and details will be provided closer to the event.

The Neo4j office has a small capacity so please RSVP ASAP so that we can keep to our capacity requirements

Agenda:

05:30 - 05:50 PM (20 mins): A journey through the GraphQL validation system

Speaker: Darrell Warde

Organization: Neo4j - https://neo4j.com

Description: Darrell has recently spent a lot of time in and around the extensible GraphQL validation system. What started as a simple rule to fill a gap in the default rule set, soon turned into a plethora of custom rules to validate every detail of schema business logic in the Neo4j GraphQL Library. He will walk through some basic rules, and demonstrate how the system has been used to implement more complex logic.

05:50 - 06:00 PM (10 mins): Unify Data Sources at the Edge

Speaker: Jamie Burton

Organization: Grafbase - https://grafbase.com/

X Handle: https://twitter.com/notrab

Description: Combine multiple APIs and databases into a single centralized GraphQL API that you can enhance with auth, permissions, and caching, fully managed and deployed to the edge with Wasm.

06:00 - 06:10 PM (10 mins): Guild’s GraphQL Architecture Show & Tell

Speaker: Taz Singh

Organization: Guild - https://guild.host/

X Handle: https://twitter.com/tazsingh

Description: Curious about how a consumer-grade social application’s data architecture has been designed? Taz will review the end-to-end GraphQL architecture used at Guild. Everything from Relay to Persisted Operations cached on Cloudflare Workers to efficient Postgres schema resolution. The session is intended to be half show-and-tell and half open discussion with the audience.

06:10 - 06:30 PM (20 mins): Improving the GraphQL developer experience on LEGO.com

Speaker: Miles Bardon

Organization: LEGO - Lego.com

X Handle: https://twitter.com/tohaker

Description: At LEGO.com, we have made great strides in stabilizing development cycles in our GraphQL gateway. We'll discuss the issues we used to have, how we used community tools to fix them, and where we're looking to go from here.

06:30 - 06:40 PM (10 mins): GraphQL Observability

Speaker: Dan Starns

Organization: Rocket Connect - https://rocketconnect.co.uk/

X Handle: https://twitter.com/dan_starns

Description: So you spent all this time building and deploying your GraphQL API but your users are reporting slow queries and crashes. Before you can pinpoint those issues you first need to know how many requests you are getting, what each query was, and what’s going on in your resolvers. Join Dan where you will learn what observability is, how you can install it onto your GraphQL API, and how you can use it to improve your user's experience.

06:40 - 7:00 PM (20 mins): GraphQL without Relay is not worth it

Speaker: Tom Harding

Organization: Hasura - https://hasura.io/

Description: GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and how GraphQL without Relay leads us to reinvent the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!

07:00 - 7:10 PM (10 mins): GraphQL and caching, when to make it more RESTful

Speaker: Endre Vegh

Organization: Formidable https://formidable.com/

X Handle: @endre_vegh

Description: We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.

That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.

How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?

Future events:

GraphQLConf 2023 in SF on September 19-21, 2023:

https://graphql.org/conf/

Presentations

Darrell Warde

A journey through the GraphQL validation system

Darrell has recently spent a lot of time in and around the extensible GraphQL validation system. What started as a simple rule to fill a gap in the default rule set, soon turned into a plethora of custom rules to validate every detail of schema business logic in the Neo4j GraphQL Library. He will walk through some basic rules, and demonstrate how the system has been used to implement more complex logic.

Jamie Barton

Unify Data Sources at the Edge

Combine multiple APIs and databases into a single centralized GraphQL API that you can enhance with auth, permissions, and caching, fully managed and deployed to the edge with Wasm.

Taz Singh

Guild’s GraphQL Architecture Show & Tell

Curious about how a consumer-grade social application’s data architecture has been designed? Taz will review the end-to-end GraphQL architecture used at Guild. Everything from Relay to Persisted Operations cached on Cloudflare Workers to efficient Postgres schema resolution. The session is intended to be half show-and-tell and half open discussion with the audience.

Miles Bardon

Improving the GraphQL developer experience on LEGO.com

At LEGO.com, we have made great strides in stabilizing development cycles in our GraphQL gateway. We'll discuss the issues we used to have, how we used community tools to fix them, and where we're looking to go from here.

Dan Starns

GraphQL Observability

So you spent all this time building and deploying your GraphQL API but your users are reporting slow queries and crashes. Before you can pinpoint those issues you first need to know how many requests you are getting, what each query was, and what’s going on in your resolvers. Join Dan where you will learn what observability is, how you can install it onto your GraphQL API, and how you can use it to improve your user's experience.

Tom Harding

GraphQL without Relay is not worth it

GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and how GraphQL without Relay leads us to reinvent the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!

Endre Vegh

GraphQL and caching, when to make it more RESTful

We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.

That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.

How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?

Platform Sponsors

Liveblocks is real-time infrastructure to create collaborative experiences like Figma & Notion in a matter of days, not months. Our toolkit is purpose-built for the JS, React, and Next.js ecosystem.

https://liveblocks.io

Clerk simplifies the process of adding authentication & user management to get you up and running in minutes. Our product is purpose-built for Next.js, React and the modern web.

https://clerk.com

We missed you this time around!

Platform Sponsors

Clerk simplifies the process of adding authentication & user management to get you up and running in minutes. Our product is purpose-built for Next.js, React and the modern web.

https://clerk.com

Liveblocks is real-time infrastructure to create collaborative experiences like Figma & Notion in a matter of days, not months. Our toolkit is purpose-built for the JS, React, and Next.js ecosystem.

https://liveblocks.io

September Meetup

London GraphQL

Sep

7

Thursday, September 7th

from 4:30PM to 6:30PM UTC

In-Person

Address available to attendees

Online

Link available to attendees

This event will be held at Neo4j offices.

Containing topics around, Grafbase, Hasura, Neo4j, and Open Telemetry.

Will be live-streamed and details will be provided closer to the event.

The Neo4j office has a small capacity so please RSVP ASAP so that we can keep to our capacity requirements

Agenda:

05:30 - 05:50 PM (20 mins): A journey through the GraphQL validation system

Speaker: Darrell Warde

Organization: Neo4j - https://neo4j.com

Description: Darrell has recently spent a lot of time in and around the extensible GraphQL validation system. What started as a simple rule to fill a gap in the default rule set, soon turned into a plethora of custom rules to validate every detail of schema business logic in the Neo4j GraphQL Library. He will walk through some basic rules, and demonstrate how the system has been used to implement more complex logic.

05:50 - 06:00 PM (10 mins): Unify Data Sources at the Edge

Speaker: Jamie Burton

Organization: Grafbase - https://grafbase.com/

X Handle: https://twitter.com/notrab

Description: Combine multiple APIs and databases into a single centralized GraphQL API that you can enhance with auth, permissions, and caching, fully managed and deployed to the edge with Wasm.

06:00 - 06:10 PM (10 mins): Guild’s GraphQL Architecture Show & Tell

Speaker: Taz Singh

Organization: Guild - https://guild.host/

X Handle: https://twitter.com/tazsingh

Description: Curious about how a consumer-grade social application’s data architecture has been designed? Taz will review the end-to-end GraphQL architecture used at Guild. Everything from Relay to Persisted Operations cached on Cloudflare Workers to efficient Postgres schema resolution. The session is intended to be half show-and-tell and half open discussion with the audience.

06:10 - 06:30 PM (20 mins): Improving the GraphQL developer experience on LEGO.com

Speaker: Miles Bardon

Organization: LEGO - Lego.com

X Handle: https://twitter.com/tohaker

Description: At LEGO.com, we have made great strides in stabilizing development cycles in our GraphQL gateway. We'll discuss the issues we used to have, how we used community tools to fix them, and where we're looking to go from here.

06:30 - 06:40 PM (10 mins): GraphQL Observability

Speaker: Dan Starns

Organization: Rocket Connect - https://rocketconnect.co.uk/

X Handle: https://twitter.com/dan_starns

Description: So you spent all this time building and deploying your GraphQL API but your users are reporting slow queries and crashes. Before you can pinpoint those issues you first need to know how many requests you are getting, what each query was, and what’s going on in your resolvers. Join Dan where you will learn what observability is, how you can install it onto your GraphQL API, and how you can use it to improve your user's experience.

06:40 - 7:00 PM (20 mins): GraphQL without Relay is not worth it

Speaker: Tom Harding

Organization: Hasura - https://hasura.io/

Description: GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and how GraphQL without Relay leads us to reinvent the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!

07:00 - 7:10 PM (10 mins): GraphQL and caching, when to make it more RESTful

Speaker: Endre Vegh

Organization: Formidable https://formidable.com/

X Handle: @endre_vegh

Description: We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.

That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.

How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?

Future events:

GraphQLConf 2023 in SF on September 19-21, 2023:

https://graphql.org/conf/

Presentations

Darrell Warde

A journey through the GraphQL validation system

Darrell has recently spent a lot of time in and around the extensible GraphQL validation system. What started as a simple rule to fill a gap in the default rule set, soon turned into a plethora of custom rules to validate every detail of schema business logic in the Neo4j GraphQL Library. He will walk through some basic rules, and demonstrate how the system has been used to implement more complex logic.

Jamie Barton

Unify Data Sources at the Edge

Combine multiple APIs and databases into a single centralized GraphQL API that you can enhance with auth, permissions, and caching, fully managed and deployed to the edge with Wasm.

Taz Singh

Guild’s GraphQL Architecture Show & Tell

Curious about how a consumer-grade social application’s data architecture has been designed? Taz will review the end-to-end GraphQL architecture used at Guild. Everything from Relay to Persisted Operations cached on Cloudflare Workers to efficient Postgres schema resolution. The session is intended to be half show-and-tell and half open discussion with the audience.

Miles Bardon

Improving the GraphQL developer experience on LEGO.com

At LEGO.com, we have made great strides in stabilizing development cycles in our GraphQL gateway. We'll discuss the issues we used to have, how we used community tools to fix them, and where we're looking to go from here.

Dan Starns

GraphQL Observability

So you spent all this time building and deploying your GraphQL API but your users are reporting slow queries and crashes. Before you can pinpoint those issues you first need to know how many requests you are getting, what each query was, and what’s going on in your resolvers. Join Dan where you will learn what observability is, how you can install it onto your GraphQL API, and how you can use it to improve your user's experience.

Tom Harding

GraphQL without Relay is not worth it

GraphQL has helped the industry realize the benefit of having typed APIs. But does that mean that if we switch over to a typed API like gRPC or OpenAPI then GraphQL is overkill? In this session, I want to discuss how GraphQL with Relay is critical to UI development and how GraphQL without Relay leads us to reinvent the wheel on state management and API libraries again and again. And also as a corollary, how using GraphQL without Relay might not really be worth it!

Endre Vegh

GraphQL and caching, when to make it more RESTful

We currently worked with an API that had to scale to serve multiple regions and millions of users. Introducing caching for such numbers is a common and battle-tested way to reduce costs. With services like Stellate, this is no longer impossible even when using GraphQL.

That is great news, however, also poses some challenges. We need to pay attention to how structure our types so we can fully utilize caching.

How to rethink some GraphQL schema designs so we can have the best of the data-driven paradigm of GQL and have amazing caching capabilities at the same time?

Guild
Got feedback or questions?
Contact Us: