{"id":5813,"date":"2023-06-25T10:23:40","date_gmt":"2023-06-25T10:23:40","guid":{"rendered":"https:\/\/youngitconsulting.de\/staging\/2187\/?p=5813"},"modified":"2023-07-08T07:14:12","modified_gmt":"2023-07-08T07:14:12","slug":"graphql-in-liferay-dxp","status":"publish","type":"post","link":"https:\/\/youngitconsulting.de\/staging\/2187\/graphql-in-liferay-dxp\/","title":{"rendered":"GraphQL in Liferay DXP"},"content":{"rendered":"

 <\/p>\n

\"\"<\/p>\n

Checkout the flow diagram here\u00a0<\/a><\/p>\n

\n
\n
\n
\n
\n

What is GraphQL ?<\/span><\/h1>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n

GraphQL is basically a query language to read or mutate data in API . In simple words its a way to call API for read and write purpose using query like syntax . Using GraphQL feels like you are querying an API service instead of a database . This was developed by Facebook .<\/span><\/p>\n

\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n
\n
\n

Challenges with REST<\/span><\/h1>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n

REST API calls has lot of advantages which is well known to developers but at the same time there are few drawbacks which REST API calls doesn’t address . Lets talk about few of them<\/span><\/p>\n

Over fetching<\/span>: This is when the API endpoint provides way more information than required by the client.<\/span><\/p>\n

Under fetching<\/span>: This is when the API endpoint doesn\u2019t provide all of the required information. So, the client has to make multiple requests (API Calls) to get everything the application needs.<\/span><\/p>\n<\/div>\n<\/div>\n

\"\"<\/p>\n

\n
\n
\n
\n

<\/h1>\n

When to use GraphQL ?<\/span><\/h1>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n
\n

Architectural Scenarios<\/span><\/h4>\n