REST VS GRAPHQL

Mach and Headless platforms are now being rapidly adopted by brands and retailers to deliver digital experiences Native cloud, APIs and Microservices are a massive leap forward in delivering more composable architectures and providing more agility for businesses, But there is a design gap between that of the consumable services of MACH platforms and the development of digital experiences and its this gap that GraphQL tries to close.
This video will help you understand what #GraphQL is and how it fits into Mach and headless architectures, as well as understand its differences with REST APIs.

See more of my articles on linkedin

Most of what I have learned in the MACH / #HeadlessArchitecture world has been while building Amplience headless CMS, DAM and dynamic media services take a look at the Amplience Website and see a MACH platform in action

00:00 Introduction to REST vs GraphQL
00:42 REST APIs design gap
04:08 What is GraphQL
05:39 The benefits of GraphQL

[Adam-eeok]

I have been going though your videos and I can't thank you enough for breaking this down!

[mrabetrafik]

thanks for sharing these helpful videos.
isn't using GQL simply pushing the REST API overfetching and underfetching issues to the resolvers? it sounds like it's an improvement for the frontend app but the end to end data requests from the micro services will still have the overfetching and underfetching issues

[GordanaMinovska]

This is high quality content! Much appreciated, thank you!