GraphQL
	- A way to define communication between backend and frontend
	- A competitor to REST API
	
	Why?
		- If you have a usecase where you want to combine data fetched from multiple different resources.
			You want to show list of posts along with their authors data, however the post is a resource different from the author resource.
			This is called under-fetching. Meaning that the endpoint doesn't return enough data.
		- If you want to select only a few properties of  a single item, for example you want to get the name and age of the author and exclude other fields, that's for one page however for another page you want all the fields of the author item. In order to do this with REST you will introduce two different endpoints for the same resource!!.
		
	
