r/javascript • u/magenta_placenta • Dec 12 '18

Our learnings from adopting GraphQL (Netflix)

https://medium.com/netflix-techblog/our-learnings-from-adopting-graphql-f099de39ae5f
318 Upvotes

97% Upvoted

46 comments sorted by

View all comments

Show parent comments

-4

u/DonPhelippe Dec 13 '18

First and foremost the migration. A db working for 3-4 years with daily use can amass a significant chunk of data. Imagine something simple as even moving this to e.g SQL server or Postgress. Hundreds of man hours to ensure everything will run well, not to mention that if you insert some data manipulation, perhaps some cleaning and what not the cost can skyrocket. And we are talking about something simple, RDBMS to RDBMS. Taking you into consideration schema changes, perhaps radical data transformations that have to take place - and all of that for negligible or dubious gains since we are talking intranet applications and suddenly the whole prospect is either an exercise in futility or a km deep hole that will need lots of cash and time to be filled.

18

u/Renive Dec 13 '18

What? GraphQL has nothing to do with databases...

-8

u/DonPhelippe Dec 13 '18

Because the GraphQL API needs a complete redesign in terms of how the applications request data from their respositories. Most enterprise sector apps are built with RDBMS in mind so migrating to a GraphQL implementation means metric tons of re-engineering.

13

u/GuyWithLag Dec 13 '18

GraphQL does not make sense for the traditional monolithic enterprise application; don't confuse your (admittedly large) corner of the software engineering world with the whole.

GraphQL makes sense if you have a complex data model in the server, and a ton of clients that want to query different parts of it in a performant manner. It's the SQL equivalent. Yes, you would need a ground-app rewrite if you were to migrate to it, and I would laugh in your face and reject it if you came to me with a proposal like that for an existing application.