Lightning Talk: REST vs Graphql

[gycgabriel]

Topic: Using Graphql vs REST API PUNCH: Instagram, Github, Facebook use graphql WIIFY: Next time, you can tell your boss why they should use graphql If your future workplace uses Graphql, you won’t appear lost and have something to say

Agenda:

• What is Graphql
• Benefits of Graphql vs REST
• Use cases for each Key points:
  1. Fetch only the required data to minimize payload
  2. Support API requests for various clients without tailored endpoints
  3. Decouple frontend-backend for rapid development

Call to action/big idea: Leverage Graphql for high-traffic interlinked data in applications

Impact: Know: What Graphql is Believe: Graphql is a good in some cases over REST Do: Provide graphql endpoints for your application if it fits the use case

Slides: https://docs.google.com/presentation/d/1SZ6GZqqZELp3bDjKOsKgxPbjB5zBXJukORTa8QOE6xQ/edit?usp=sharing

[gycgabriel]

Answer prof's question regarding mutations: Graphql can update data via Mutations: https://stackoverflow.com/questions/37906261/how-to-update-data-with-graphql

[gycgabriel]

C1( week 12)

New title: GraphQL is faster and lighter than REST

Updated slides: https://docs.google.com/presentation/d/1qTOQxuntEFVkVkA6rJclKaXtVvSUAp3NFXwyslef7Yk/edit?usp=sharing