Since its release in 2015, GraphQL has become the alternative to REST. It gives frontend developers the flexibility they had craved for for so long.
Over are the days of begging backend developers for one-purpose-endpoints. Now a query can define all the data that is needed and request it in one go, cutting latency down considerably.
Is there life after COVID-19? Of course there is, even though it may be quite different, and it may be hard to get there. But there’s one thing in common in the "before" and "after" pictures: science and technology as the cornerstones of modern society, for better or worse.
We have argued before that Knowledge Graph is a technology that enables other technologies to accelerate their growth, and it also enables humans to take stock of their own knowledge. This is why the future is Knowledge Graph.
I’m going to share a deep, dark secret from my past: before I shifted to JavaScript, I was actually a Java developer. This means I have worked as both a backend and frontend developer. It also means I am uniquely qualified to share with you another dark industry secret: the things that backend developers say about frontend developers when they’re not around. Are you ready? Here we go:
But of course, let’s be honest: frontend developers also say things about backend developers when they’re not around. For example:
When discussing API design, REST or Representational State Transfer is what comes to mind first. It is a standard tool used for data retrieval from the server that accesses data by URLs.
Client applications whilst progressing into the new millennium was relatively simple. That is when REST had been developed and it became a good fit for many applications in due course of time.
REST is an API design architecture, which, in the last few years, has become the norm for implementing web services. It uses HTTP to get data and perform various operations (POST, GET, PUT, and DELETE) in JSON format, allowing better and faster parsing of data.
However, like all great technologies, REST API comes with some downsides. Here are some of the most common ones:
In this article, I will highlight how the glorious monarchical reign of REST (Representational State Transfer) APIs is declining and how the ecosystem is moving towards democracy. Today the API consumers decide what the format or protocol of the API should be.
The Hasura platform’s data microservice provides an HTTP API to query Postgres using GraphQL or JSON in a permission safe way.
You can exploit foreign key constraints in Postgres to query hierarchical data in a single request. For example, you can run this query to fetch “albums” and all their “tracks” (provided the “track” table has a foreign key to the “album” table):
