INTERFACE by apidays 2023 - GraphQL's second act, Jesse Martin, Hasura

@motleydev GraphQL's Second Act A practitioner’s tale

@motleydev whoami • Senior Sales Engineer at Hasura • GraphQL
Educator for 5+ years • Ex Digital Strategy, Branding, Consultant • 4x Dad

@motleydev whois hasura.io • Open source engine that can instantly
convert database schemas to GraphQL schemas and create SQL from from GraphQL queries. • It creates an API for your data with very robust access controls. • Supports custom business logic, ephemeral models, event triggers, REST APIs, and more. • Is hiring. 😉

@motleydev

@motleydev Fortune 500 Companies and Fast Growing Startups love Hasura
• Build new applications or add new features to an existing application • Modernize existing applications within a shorter timeframe • Replace direct database access with a scalable, performant and secure data API to create a uni fi ed and federated “Core Data Service”

@motleydev Assumptions • You know a little about what GraphQL
is • You are aware some people get angry about silly things

@motleydev Takeaways • GraphQL is becoming a universal data SDK
• GraphQL is not just for front-ends

@motleydev Strong Opinions loosely held, strongly inferred …haters gonna hate

@motleydev REST is preferred by   single service providers

@motleydev GraphQL is preferred by   multiple service consumers

Data access challenges

@motleydev Data access challenges

@motleydev REST: easy to model around deliverables

@motleydev GraphQL: easy to model around consumables

@motleydev I used the word model on purpose.

@motleydev Metcalfe’s law for GraphQL

@motleydev User Scooter Coffee Loyalty Status Battery Status Charge Stall
Coffee Shop Location Weather Menu Orders Date Recommendation Engine

@motleydev

@motleydev • Less overhead for orchestrating services • Smaller control
plane • Reusable patterns • Agnostic consumers Benefits of this approach

@motleydev Example Diagrams

Mutations / Writes Queries / Reads Common GraphQL service structure
User Order Product Login / Logout Purchase Edit Microservice REST SQL REST SQL SQL

@motleydev Data dependencies User Order Product Purchase

@motleydev Data dependencies User Order Product Purchase GET /user GET
/order GET /product POST /graphql { user { order { product { …info } } } }

@motleydev Less abstract Pending purchases Historical income / expense History
of returns Risk Assessment Network credit average Economic variables

@motleydev Less abstract Pending purchases Historical income / expense History
of returns Risk Assessment Network credit average Economic variables REST SDK REST SDK REST

@motleydev In Practice

@motleydev Healthcare Coverage Reverse ETL DORA Metrics Realtime Telematics Global
Banking Multi-tenant SaaS

@motleydev Angry Dissenting Opinions Everyone’s allowed to be wrong

@motleydev • It’s not what GraphQL was   created for.
• No, but it is what it was   designed for. • What about latency? • Marginally higher than optimally designed REST alternatives.   Also a solvable problem.

@motleydev Gotchas

@motleydev None.

@motleydev Latency

@motleydev New API, new Problems

@motleydev What Hasura   is going to do about it.

@motleydev Model driven • 100% Declarative • The model de
fi nes your data’s affordances (summable, group- able, etc) • The model de fi nes it’s relations and shapes.

@motleydev Model driven • GraphQL Agnostic • The tooling converts
the model to an API. • Actually, it’s what we’ve always been doing.

@motleydev But they said I couldn’t give this talk, so
watch API Days NYC. ;)

@motleydev Where to find more • hasura.io • @hasuraHQ •
@motleydev • HasuraCon

@motleydev Queries?

INTERFACE by apidays 2023 - GraphQL's second ac...

INTERFACE by apidays 2023 - GraphQL's second act, Jesse Martin, Hasura

More Decks by apidays

Other Decks in Programming

Featured

Transcript