Our great sponsors
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
graphql-zeus
GraphQL client and GraphQL code generator with GraphQL autocomplete library generation ⚡⚡⚡ for browser,nodejs and react native ( apollo compatible )
-
polyglot-persistence-postgresql-mysql-graphql
This repo demonstrates how to achieve polyglot persistence for PostgreSQL & MySQL using GraphQL as the layer of abstraction.
-
wundergraph-demo
This Repository demonstrates how to combine 7 APIs (4 Apollo Federation SubGraphs, 1 REST, 1 standalone GraphQL, 1 Mock) into one unified GraphQL API which is then securely exposed as a JSON API to a NextJS Frontend.
-
great-bear-postgraphile
Implementation of the Great Bear backend using Graphile (aka postgraphile aka postgraphql)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
blog-django-graphql-hasura
An example implementation of a Django Graphene GraphQL API meshed with Hasura Remote Schemas for auth.
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.
https://github.com/hasura/graphql-engine/issues/6991
General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.
This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.
Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.
[1]: https://github.com/gqless/gqless
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.
https://github.com/hasura/graphql-engine/issues/6991
General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.
This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.
Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.
[1]: https://github.com/gqless/gqless
This feature is available with WunderGraph. You can configure Auth, caching, live query polling etc. at a global level and override it for each individual query:
https://github.com/wundergraph/polyglot-persistence-postgres...
https://github.com/wundergraph/wundergraph-demo/blob/906f72c...
This feature is available with WunderGraph. You can configure Auth, caching, live query polling etc. at a global level and override it for each individual query:
https://github.com/wundergraph/polyglot-persistence-postgres...
https://github.com/wundergraph/wundergraph-demo/blob/906f72c...
This feature is available with WunderGraph. You can configure Auth, caching, live query polling etc. at a global level and override it for each individual query:
https://github.com/wundergraph/polyglot-persistence-postgres...
https://github.com/wundergraph/wundergraph-demo/blob/906f72c...
A couple years ago I built similar backends using both technologies so they could be directly compared. The readmes take you through the architectural decisions: https://github.com/sastraxi/great-bear-postgraphile and https://github.com/sastraxi/great-bear-hasura
A couple years ago I built similar backends using both technologies so they could be directly compared. The readmes take you through the architectural decisions: https://github.com/sastraxi/great-bear-postgraphile and https://github.com/sastraxi/great-bear-hasura
+1 that's probably my favorite way of doing it - https://github.com/martin-hasura/blog-django-graphql-hasura Even Django REST Framework and Hasura works pretty well cause you get auth + then if you want to do functions you get that for 'free' as well
Related posts
- Hasura V3 Engine is in alpha
- Hasura: Instant GraphQL on your Postgres data
- 🤩 20 Awesome Tools For Your Web Dev Toolkit 🛠️
- Writing filters, sorting and pagination for all my queries is exhausting and repetitive. Is there a better way?
-
Hasura VS graphweaver - a user suggested alternative
2 projects | 23 Aug 2023