Explain REST Api and Graph Api in SharePoint

I recommend Microsoft Graph API. I know it is a proxy to actual Sharepoint, OneNote, Planner, and etc API, but the way they are improving graph api day by day makes me think it is going to last for a good time. Let's say if you are writing an app that wants to connect with many Microsoft apps endpoints, having one class that handles all the graph api requests is enough instead of looking for specific apps endpoints.

Performance: I have been using Microsoft graph api for most of SharePoint related work and it works good and fast. I use Graph explorer to check out the graph if it actually works before implementing it in the app.

Functionality Coverage: Obviously graph is a proxy of a real api so it won't cover all the processes you need to do in SharePoint. For example, I had to create a Sharepoint Group which I could not find a way via graph api. But I assume as more people vote on those requests, the graph api is bringing those new possible proxy endpoints too. But again if your app is only working with Sharepoint then I believe I would stick to SharePoint API. In favor of Graph API, they also have something called delta query and subscription notification to see changes in the files and documents.

• An architectural style for web services.
• Allows communicating between two software programs through HTTP.
• You can use different methods/verbs like GET, POST, PUT and DELETE
• It is essentially based on the user context.

Graph Api in SharePoint:

• Allows accessing the SharePoint data but not only data. you can access the wide resources provided by MS365 Tenant.
• It is based on the entire environment.
• It becomes useful when you wish to link several resources types in one point.