https://github.com/capaj/node-rest-vs-graphql

comparison of two implementations of the same API using REST and Graphql
https://github.com/capaj/node-rest-vs-graphql

Last synced: over 1 year ago
JSON representation

comparison of two implementations of the same API using REST and Graphql

• Host: GitHub
• URL: https://github.com/capaj/node-rest-vs-graphql
• Owner: capaj
• License: mit
• Created: 2022-02-04T14:50:45.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2022-02-11T07:37:42.000Z (over 4 years ago)
• Last Synced: 2025-02-10T03:27:41.322Z (over 1 year ago)
• Language: TypeScript
• Size: 387 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# node-rest-vs-graphql

comparison of two implementations of the same dead simple CRUD API using REST and Graphql

This showcase was created mostly to refute misleading myths developers tell themselves about graphql having more overhead than REST.

Both branches have the same CRUD functionality over a single db table:

- query for blogpost with filtering by from and to dates

- query to fetch a single blogpost

- mutation to create a new post, update existing one and delete a blogpost

Graphql schema is built using typegraphql, but other frameworks are similar in verbosity.

For both we have a tool for playground+documentation: 

- in REST, we have swagger docs:

![picture 1](images/a33d5b927105e24a9fb73b51ecd97c2c0c3243a53aea9beadaecfade7cae9fcb.png)

 - graphql has graphiql bundled with mercurius:

![picture 1](images/7bd100537378974ff6331eb1f9ebfb3e759fb95e59724899c9594093c7d5c217.png)