> We migrated Netflix’s mobile apps to GraphQL with zero downtime
Is "zero downtime" relevant here?
For example, when migrating a database that is the source-of-truth for data, then yeah, downtime is something you have to contend with. But for a client-server API change, isn't it trivial? Companies do this all the time -- expose a new version of an API then gradually migrate clients over.
(It's definitely not a trivial task overall! For example, you need thorough testing to make sure you don't break existing functionality and the article does talk about that.)
I don't know, you said isn't trivial then you said it's not trivial! :D It's a colossal effort if you are at Netflix size, they support probably the largest number of client devices on the planet.
Is "zero downtime" relevant here?
For example, when migrating a database that is the source-of-truth for data, then yeah, downtime is something you have to contend with. But for a client-server API change, isn't it trivial? Companies do this all the time -- expose a new version of an API then gradually migrate clients over.
(It's definitely not a trivial task overall! For example, you need thorough testing to make sure you don't break existing functionality and the article does talk about that.)