---
title: "Discussion on \"GraphQL (microservices) architecture by Apollo\" | Hashnode"
description: "Discussion on \"GraphQL (microservices) architecture by Apollo\". Why use GraphQL and not REST\nIf you look from the perspective of the client (the frontend) there are a few challenges with REST API's when getting the data.\nChallenges with REST\nFor years we are using REST API's because they were more convenient than..."
url: "https://hashnode.com/posts/graphql-microservices-architecture-by-apollo/5e201a417a1d3fcc5902b1c5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [GraphQL (microservices) architecture by Apollo](https://hasnode.byrayray.dev/graphql-microservices-architecture-by-apollo?utm_source=hashnode&utm_medium=feed)

Why use GraphQL and not REST If you look from the perspective of the client (the frontend) there are a few challenges with REST API's when getting the data. Challenges with REST For years we are using REST API's because they were more convenient than...

Jan 16, 2020 · hasnode.byrayray.dev  
Read the article

-   [#graphql](https://hashnode.com/tag/graphql)
-   [#apollo](https://hashnode.com/tag/apollo)
-   [#microservices](https://hashnode.com/tag/microservices)

## Written by

[Dev By RayRay](https://hashnode.com/@devbyrayray)

@devbyrayray · Netherlands

  
[View profile](https://hashnode.com/@devbyrayray)

Tech Lead / Lead Developer in the 🇳🇱 https://byrayray.dev/

🚀 Tech Lead / Lead Developer 🔥 Writing about CSS, JavaScript, Typescript, Angular, Vue.js, Nuxt.js, Serverless functions, and a lot more web-related topics. https://byrayray.dev/

## Responses

Markdown supported · ⌘↵ to post

No responses yet.