I can remember when Git began to replace Subversion, but a lot of companies resisted the trend, because Git was so radically different. Subversion was comfortable: everything was centralized, and the revision numbers went up in an orderly fashion: 1, 2, 3, 4, 5, 6... You always knew where you were in history, with Subversion. It was clear that Git was better in some fundamental way, and yet it took effort to understand it, conceptually, at first.<p>I feel like the same thing is happening now with GraphQL versus REST. On some level it seems like GraphQL is altogether better than REST, but we don&#x27;t see a mad rush to adopt GraphQL, because it represents a big shift in thinking, and those of us who just spent the last 10 years creating RESTful interfaces, we are a bit slow to throw out all of our work and start over with GraphQL. Also, the frontend needs to change as much as the backend, so it requires a full re-write of everything.<p>All the same, a title like &quot;Scale vs. Node.js as a RESTful back end server&quot; does strike me as an anachronism in 2016. Who cares? I doubt I will ever again build a RESTful interface. Rather, on the project I&#x27;m working on right now, we are getting rid of the RESTful interface and we are looking at our GraphQL options:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;chentsulin&#x2F;awesome-graphql" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;chentsulin&#x2F;awesome-graphql</a><p>Is Scala or Node.js the best option for building a GraphQL server? That would be an interesting article.