Ruwan Xaviour Fernando

Rapid GraphQL API Development with PostGraphile

What if you could build a performant GraphQL API without writing a single resolver? Learn how a database-first approach makes it possible.

Rapid GraphQL API Development with PostGraphile
#1about 6 minutes

The buy vs build dilemma in media platforms

Axinom's product strategy evolved to offer modular microservices that solve the customer's choice between buying a monolith or building from scratch.

#2about 4 minutes

Choosing a tech stack for customizable services

The technology stack of Node.js, GraphQL, and PostgreSQL was selected to support expressive APIs and a relational data model for media content management.

#3about 5 minutes

Adopting a database-first API development philosophy

A development philosophy centered on treating the database as the API, maximizing auto-generation, and ensuring performance by default led to adopting PostGraphile.

#4about 6 minutes

Comparing database-first with schema-first and code-first

PostGraphile's database-first approach, where the SQL schema is the single source of truth, is contrasted with traditional schema-first and code-first GraphQL patterns.

#5about 7 minutes

Extending GraphQL schemas with PostGraphile plugins

The extensive plugin system in PostGraphile allows for auto-generating complex filters and adding custom business logic by extending the schema or wrapping resolvers.

#6about 5 minutes

Solving the N+1 query problem automatically

PostGraphile avoids the common GraphQL N+1 query problem by generating efficient SQL joins directly, rather than relying on less performant ORM patterns or data loaders.

#7about 4 minutes

Live demo of generating an API from a database

A live demonstration showcases running the PostGraphile CLI against a PostgreSQL database to instantly generate a full-featured GraphQL API for queries and mutations.

#8about 6 minutes

Q&A on pagination and database compatibility

Audience questions are answered regarding PostGraphile's built-in support for cursor-based pagination and its specific design for PostgreSQL, not other databases.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Videos

See all videos
GraphQL: Does it replace SQL, REST or Something Else?28:12

GraphQL: Does it replace SQL, REST or Something Else?

Gregor Bauer

Putting the Graph In GraphQL With The Neo4j GraphQL Library47:48

Putting the Graph In GraphQL With The Neo4j GraphQL Library

William Lyon

The Great API Debate: REST, GraphQL, or gRPC?28:16

The Great API Debate: REST, GraphQL, or gRPC?

Alexis Yushin

GraphQL + Apollo + Next.js: A Lovely Trio40:45

GraphQL + Apollo + Next.js: A Lovely Trio

Josh Goldberg

GraphQL Mesh – Why GraphQL between services is the worst idea and the best idea at the same time!34:28

GraphQL Mesh – Why GraphQL between services is the worst idea and the best idea at the same time!

Uri Goldshtein

Event based cache invalidation in GraphQL36:58

Event based cache invalidation in GraphQL

Simone Sanfratello

Rethinking Reactive Architectures with GraphQL 41:06

Rethinking Reactive Architectures with GraphQL

David Leitner

How Gatsby Cloud's real-time streaming architecture drives <5 second builds42:10

How Gatsby Cloud's real-time streaming architecture drives <5 second builds

Kyle Mathews

From learning to earning

Jobs that call for the skills explored in this talk.