 Hi everyone. So I'll be talking more about why GraphQL over REST. So before I start a little about myself, next slide. So my name is Anupam Dagar. I'm a GitHub Campus expert from IIT, Allahabad, India. I have been a software developer at Hasora, a former contributor at Zulep and currently contributing to Fawcetia. Coming to my community, I'm a community leader of Geekhewin and I have been the main core team member of Organizing the Hackathon or the Hackathon. Next slide please. So why GraphQL over REST? So the main part is why people choose to GraphQL over REST is that it resolves the two of the main issues which are found with the REST. Next slide please. So I'll be just telling this about more by taking an example. Next slide. So yeah, the example comprises of a simple feed app. So a simple feed app may consist of many posts and the posts may have many of the attributes like the title, authority, view, count, like count and dates, etc. Next slide. So here are two resources, the users and the posts. So users is like one database and the posts another database and both are linked together with a foreign key. Next slide. So here you can see a sample query in REST to fetch the posts. So you do one query to get the posts and you get the user ID inside it and you want to show the user ID also. So you do another request with the user ID to get the user's detail. Next slide. So yeah, so suppose the project has been running for about two years and the design specifications has gained and they say, okay, we don't want to show the view count in the post. So what do you do? So next slide. So the main component which comes here is like you will first of all think to discard the view count post directly. And other thing is like you will just like don't use the view count field which is getting from the response. So next slide. So yeah, so here are the two main issues with the REST. One is the like multiple round trips being used in the first case when you need to show the user count and the post count. So you did two requests to get the single resource completed. Other is like over fetching of data in the second case when you have to like discard the view count field from the response. So it's like over fetching of data and next part is like documenting API becomes difficult because when you have a lot of endpoints being there. Next slide. So yeah, how GraphQL solves these issues? So GraphQL solves these issues by providing a single endpoints to all your data needs. So what you do is like you specify your dvname and the column which you want from the request and it fetches the data from all over there. So yeah, you get and update only the data you need or delete anything you just require. So in suppose I have to discard the view count so in my get query, so I'll just remove that view count field and I won't get that attribute in my response. And find the documenting the API is easy because you don't have to you have a single endpoint and so you just change over the which fields you need to get and you need to meet it. Next slide. So that's it. You to get the more updates like stay connected with me. You can follow me on Twitter. Thank you very much.