Hasura SDK integrates GraphQL platform with more data sources
At its HasuraCon ’22 conference today, Hasura announced the early release of a software development kit (SDK) that extends the reach of its GraphQL platform to additional data sources.
In addition, Hasura provides generally available integrations with the GitHub repository, support for OpenTelemetry traces within the Hasura Cloud Platform, and Microsoft SQL event triggers.
Finally, Hasura Cloud can now be deployed on Google Cloud Platform, while Hasura Cloud Enterprise Edition is now available on the Amazon Web Services (AWS) marketplace.
Hasura CEO Tanmai Gopal said that while the company already offers support for widely used data sources such as the Postgres database, there are many data sources that companies also want to be able to query via GraphQL application programming interfaces (APIs). Businesses want to be able to merge data with GraphQL no matter what repository it’s in, he added.
The open-source Hasura engine, which forms the core of the company’s offerings, automatically generates a GraphQL schema from a data source. This can then be used to speed up the development of APIs to make it easier for a wider range of developers to build applications that aggregate data from multiple sources.
This approach eliminates the backend complexity that IT teams encounter when adding GraphQL APIs to an application environment that already has a set of APIs that internal IT teams need to support, Gopal noted.
GraphQL was originally developed by Facebook, but it’s still not clear to what extent GraphQL APIs will replace REST APIs. Developers typically prefer GraphQL APIs because they offer more granular control over what data is accessed. The challenge is that the number of backend services exposing GraphQL APIs is still comparatively limited.
It’s unlikely that IT teams will replace REST APIs with GraphQL-based APIs overnight, but the percentage of new applications that rely on GraphQL APIs will steadily increase. Overall, the number of APIs used in IT environments is growing rapidly as more microservices-based applications are deployed. Each microservice generates its own API. Over time, IT teams will find themselves managing a greater variety of API types.
The challenge is that it’s not always clear who within IT organizations will be managing these APIs. They are often created by developers and left to IT operations teams to maintain. It’s not uncommon for IT teams to have hundreds, maybe thousands, of APIs to manage.
Additionally, many of these organizations are now consuming data through APIs provided by other organizations. Over time, the level of interdependence between APIs and applications will make managing application environments much more complex.
Meanwhile, DevOps teams need to extend existing DevOps workflows to both support and secure GraphQL-based APIs. The amount of sensitive data accessed through these APIs will likely accelerate the rate at which organizations adopt DevSecOps best practices. Let’s hope that happens before they wake up and find that GraphQL APIs have already spread throughout the enterprise.