All projects
backend apis
A GraphQL API over an existing REST service
Wrap a REST backend in GraphQL and confront the N+1 problem head-on.
Why it matters
GraphQL looks trivial until the first nested query fires 200 database calls. Solving that is the interesting part and the part worth showing.
What you build
- A schema designed around the client's questions
- Resolvers over an existing REST service
- Batched loading that kills the N+1
- Query depth and complexity limits
If you want more
- Add subscriptions
- Add persisted queries
Build it
Not from your database tables.
- Implement resolvers against the existing service
- Write down what GraphQL cost you here, honestly
Material for the whole build
Shows you can adopt a technology without inheriting its worst failure mode.
Get a plan built around projects like this