The story of migrating a (not so) REST API to GraphQL – the Deezer experience
| Published | |
| Reading time | 1 minute |
| Licence |  |
| Tags | Tech - Node.js - Graphql - Performance - Proofread by an LLM |
At Deezer, we decided to move from a homegrown (not really REST) API to GraphQL. Why? That’s not the point here. I’m focusing on the how.
Here’s an account of how we managed this large-scale migration and some of the challenges we faced.
Conflict of interest disclosure: Deezer is my employer 😛 for 10 years now.
This is a talk I gave at the GraphQL Paris meetup in October 2025. It gives a broad overview of the topic to fit within a 30-minute presentation slot.
If you’d like to know more about a specific aspect, let me know on social media so I can cover it in more detail next time I present on this subject.
Presentation slides
You can find the slides here (in English):
Conference video
Watch the full talk on YouTube:
Disclaimer: The video is in French, but the slides are in English.
Thanks for reading me,
Bisoux 😗
| Title | The story of migrating a (not so) REST API to GraphQL – the Deezer experience | |
| Description | A feedback on migrating a legacy API to GraphQL at scale at Deezer. | |
| Published | ||
| Updated | ||
| Type |  | |
| Reading time | 1 minute | |
| Words | 169 | |
| Translation | English | https://blog.ztec.fr/en/2025/post/rex-migration-graphql-deezer/ |
| Français | https://blog.ztec.fr/2025/post/rex-migration-graphql-deezer/ | |
| Tags | Tech - Node.js - Graphql - Performance - Proofread by an LLM | |
| Licence | Except for quoted materials, which retain their original rights and attributions, this post and its content are published under the Creative Commons(CC BY-NC-SA 4.0) liscence | |
Found a typo, or something bigger that probably killed a grammar nazy ? suggest a fix via github.
You can subscribe via
RSS to get new articles as son as they are published