I think yes

GraphQL hit in a very specific sweet spot:

- nowadays there is a huge demand for distributed systems

- these systems need a communication protocol

- GraphQL smokes competition in this regard: less traffic; flexible, different clients can decide on the shape of data; documentation and playground out of the box and always in think with the system

But then there are some less obvious bonuses:

- clients, like Apollo, can implement complex cache, so even less traffic

as step 1 of system development

- frontend/backend devs + even product owner can come together and think on a GraphQL schema. And they try to come up with types and methods very close to the business, that will reflect not implementation details, but the business aspects/domain.

And then these types can migrate into each part of the system code

Business defined types come naturally from the natural 1 step of system design. That impresses me a lot, how beautiful it is.

So, yes, I think GraphQL will evolve and will become the Universal Type System.


Freelancer (Upwork Top Rated Plus). Full-stack Azure cloud developer. JavaScript and TypeScript connoisseur.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store