By adopting Hasura, ISOS has elevated the quality and performance of its digital services. This positions ISOS to better serve clients and uphold their mission of saving lives.

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.

If you’ve ever found yourself wishing you could use Hasura-flavored GraphQL with your SQLite database, you’re in luck because today we are excited to announce the release of the Hasura Turso connector.

For GraphQL adoption to become viable for the organization, they needed Hasura's connect-and-compile approach. Hasura not only made GraphQL feasible but also satisfied additional criteria the organization had established for their chosen GraphQL solution.

In this blog, we will share our (opinionated, but grounded) perspective on why Hasura is better than Apollo for building and running production GraphQL APIs at scale in most enterprise use cases.

More so than this being GraphQL vs. REST argument, it’s important to understand that GraphQL can co-exist with REST APIs, or replace them altogether, and either choice has different implications.

Toronto-based engineering firm Tactable was first drawn to the overall value Hasura brings to backend development, and they’ve leveraged Hasura to deliver successful projects for major brands, including Shopify, Rakuten, and Walmart.

I think a big part of the hype boils down to the fact that GraphQL done right is simply better than any possible equivalent of its REST counterpart.

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.

In this post, I would like to summarize some key takeaways from the conference and how exciting the future of GraphQL looks like.