GraphQL may have crested the Peak of Inflated Expectations since, but it's reached a broad flat plateau where the weather is mild and the terrain is gentle. There have been laudable successes and no overt failures. Needs were met, products were created, wars were fought, and empires were founded.

Our new active model-based pricing upends the traditional usage-based pricing paradigm by aligning your costs with the value you receive from your API platform.

To connect backend data products with the chatbot frontend, a reliable, scalable, and secure communication mechanism is needed. This blog post posits that the link should be GraphQL.

After attempting a few DIY options, Renaissance settled on the Hasura-Snowflake connector as their preferred solution for pulling the required data from Snowflake into the app via APIs.

As backend engineers, they spent a lot of time figuring out how to connect routes to controllers, controllers to services, and services to the data access level. All of this work is replaced by Hasura.

Rather than viewing Hasura as a replacement for API gateway tools, we will highlight the incremental adoption approach, showcasing how Hasura seamlessly integrates with established API gateway platforms such as Apigee, MuleSoft, and more.

Explore ways to automate these processes to create a more streamlined and consistent development experience when working with Hasura.

When working in parallel, solutions like Apigee and Hasura form the backbone of a complete enterprise API strategy.

Building GraphQL APIs manually requires a lot of effort and resources. This post talks about how Hasura helps build GraphQL APIs eliminating the challenges and time consumed.

Hasura releases GraphQL Data Connectors alpha SDK, Streaming Subscriptions API, Hasura availability on AWS Marketplace, support for Open Telemetry as well as General Availability of a GitOps workflow with Hasura Cloud and Hasura Cloud on Google Cloud Platform.