Hasura today unveiled a Data center Application programming interfaces (API) integration repository. The repository includes a connector that makes it easier for IT departments to convert REST APIs to APIs based on the GraphQL specification.
Tanmai Gopal, CEO of Hasura, said the connector eliminates the need to write custom code to connect existing REST endpoints to a GraphQL API using an update to the transformation engine developed by Hasura. Instead, the GraphQL API model is automatically overlaid on the REST API endpoint, Gopal explained.
Originally developed by Facebook, GraphQL has become a popular alternative to REST APIs because it allows developers to retrieve data at a more granular level, which improves performance. Hasura provides an instance of a GraphQL engine that the company developed around a project that is now hosted by the GraphQL Foundation, a branch of the Linux Foundation. GraphQL provides a complete description of the data made available through an API and is organized in terms of types and fields rather than traditional endpoints. In addition to clarifying what data is available through this API, developers can use types to avoid writing manual parsing code.
Hasura claims that its engine has been downloaded over 400 million times since its introduction in 2018. It automates the repetitive work involved in matching patterns to APIs by providing common access patterns for paging, filtering , junction, configuration of authorization rules and performance tuning. Hasura also provides APIs that can connect to multiple services and data sources, integrate domain-specific authorization logic, and provide additional layers of security.
Hasura now also adds a way to create identity-specific authorization policies for any GraphQL service or data source, enforcing security by limiting patterns and fields of GraphQL APIs in a way that eliminates the need for IT teams tinker with disparate libraries and frameworks, Gopal said.
Additionally, Hasura adds support for Google Cloud to Hasura Cloud Beta, a managed API integration service that the company already provides through the Amazon Web Services (AWS) cloud. Microsoft Azure cloud support will be available in 2022, Gopal added.
It is not clear to what extent organizations are looking to replace existing REST APIs with those based on GraphQL. However, Gopal noted that there are many instances where organizations need to overlay a GraphQL API over a REST API that they might not have. For example, a software as a service (SaaS) platform that currently exposes a REST API may not have the intention of supporting GraphQL, he said.
There is no doubt that the number of GraphQL APIs in use across the enterprise is about to increase dramatically. The challenge now is to find a way to manage them with the previous generations of APIs that remain. The problem is, many of these APIs were created by developers who may not have documented the APIs they created, or in some cases never informed DevOps teams of their existence.