Editing Technical Test (section)

====REST vs GraphQL====
=====GraphQL Advantages=====
No more Over- and Underfetching. In GraphQL, you specify exactly what you need. REST, requires multiple requests and API reflects UI. When UI changes, over/under fetching the API occurs.
* GraphQL can decouple frontend from backend.
* API evolution is possible without versioning.
* It is statically typed, so you do not need to define variable before using it.
* No over or under fetching of data.
* It is language and HTTP agnostic.
* Documentation of GraqphQL comes with no extra cost.
* It helps you to save bandwidth.
=====GraphQL Disadvantages=====
* GraphQL uses a single endpoint instead of following the HTTP caching.
* Adds complexity / overkill for small applications

=====REST Advantages=====
industry standard for companies deploying APIs
* Services of REST can be scaled to achieve high performance to span client demand.
* The API of REST can be served from more than one server.
* REST allows you to store frequently used information in the memory.
* REST has a uniform interface.
* Resources can be easily accessed by name.
* Database resource in an application can be quickly mapped with a REST API endpoint.
* It has a simple architecture and pattern.
=====REST Disadvantages=====
* If you have to retrieve any data from two endpoints, you need to send two separate requests to API.
* There is no way to get limited fields.