Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Sandip Devarkonda
Supergraph: A Solution for API Orchestration and Composition
Supergraph: A Solution for API Orchestration and Composition sponsor-hasura,sponsored-post-contributed, Image from eamesBot on Shutterstock. In the previous post in this series, we discussed the complexities of building and consuming APIs in enterprise data landscapes. These environments involve multiple data domains managed by different teams and numerous applications, leading to challenges due to constrained resources and conflicting goals.
Solving API Integration and Aggregation With Supergraph
Solving API Integration and Aggregation With Supergraph sponsor-hasura,sponsored-post-contributed, Image from Zakharchuk on Shutterstock It’s hard to be in the business of building or consuming APIs in enterprise data/API landscapes. These complex landscapes typically have the following characteristics: Multiple data domains, each managed/owned by one engineering team (multiple producers of APIs).
From Basics to Supergraph: A practical guide for your GraphQL adoption journey
When implemented effectively, the evolution of GraphQL within an organization often transitions from a singular graph, or subgraph, to an expansive network of interconnected graphs, known as a supergraph, through the process of GraphQL federation. This progression, however, is not mandatory for entities managing a single or a few domain databases. When such expansion does occur, it usually unfolds in a cyclical manner, with the continuous development of new subgraphs.
The Architecture of a High-Performance GraphQL to SQL Engine
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): As you may have guessed, the queries can traverse tables to an arbitrary depth.
Understanding the Rise of GraphQL: GraphQL vs. a JSON DSL
It turns out that GraphQL is pretty awesome. I didn’t always see it that way. The first few times I ran across GraphQL, I was pretty skeptical of its touted benefits because the cost of putting together a GraphQL system seemed too high. It also seemed to me that all the benefits of GraphQL could still be achieved by just creating a custom JSON DSL (query language using JSON).
A Case for GraphQL in Enterprise
Gartner positions APIs at the forefront of Digital Transformation or similar CIO initiatives. Sharing data-driven insights and building efficient workflows to deliver value to stakeholders largely entails building and managing APIs for applications. GraphQL, a query language specification developed and open-sourced by Facebook, is rapidly revolutionizing the API Lifecycle Management (APLM) space.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Sandip
Contact Sandip, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack