The document discusses productizing data by delivering it as a managed GraphQL API service. It notes the need to provide self-serve access to both internal and external developers across different data sources and storage types, while ensuring performance, security, and quality of service. The document contrasts building a GraphQL API with exposing direct data access and outlines some of GraphQL's pros like flexibility and its cons like requiring a new way of thinking about caching, rate limiting, and security. It concludes with a demo of a GraphQL API that can query, mutate, and subscribe across databases.

1. @tanmaigo // @HasuraHQ
Productify your data with
GraphQL APIs
Tanmai Gopal / CEO / Hasura

2. @tanmaigo // @HasuraHQ
Topics
- Motivating delivering your data as a service
- Business need: Self-serve, different types of data, different types of storage
- Technical needs
- Functional: reads, writes, streams/events
- NFR: performance/caching, security, QoS
- Pros/cons of GraphQL
- Self-serve
- Queries, mutations, subscriptions
- NFR needs to be thought about
- Flexible querying & subscriptions: Demo with single database and across databases
- Authorization
- Caching, Security and QoS

3. @tanmaigo // @HasuraHQ
Why should I productify my data?
- Data is exploding and it is everywhere
- Internal and external developers want access to this data
- What if we think of delivering our data as a managed service? A SaaS API
experience for your data
- Philosophically, should be ”self-serve“!

4. @tanmaigo // @HasuraHQ
Technical requirements
- Functional requirements:
- Read
- Write
- Subscribe: Events & notifications
- Non-functional requirements:
- Performance
- Security
- Observability
- QoS

5. @tanmaigo // @HasuraHQ
To API or not?
- No API
- Direct access to data sources
- Operational problem: TCP and not a stateless HTTP API
- Control problem: Hard to control and govern access
- API
- Needs to support the technical primitives we want
- Needs to be flexible. Eg: SQL is awesome, APIs are so restrictive :(

6. @tanmaigo // @HasuraHQ
GraphQL API
- Pros
- Flexible. Like SQL but for APIs
- Unify across databases
- Modern primitives: query / mutate / subscribe / stream
- Cons
- It’s a new API thing
- Move from “endpoint” thinking to “query” thinking:
- Caching
- Rate-limiting
- Security

7. @tanmaigo // @HasuraHQ
@tanmaigo // @HasuraHQ
Demo :)

8. @tanmaigo // @HasuraHQ
Thank you!
@tanmaigo