p/hasura
Universal data access layer for next-gen apps and AI
Kevin William David
Hasura Event Triggers — Trigger serverless functions on database events.
Featured
5

Hasura GraphQL Engine is a blazing-fast GraphQL server that gives you instant, realtime GraphQL APIs over Postgres, with webhook triggers on database events for asynchronous business logic. You can now call webhooks or serverless functions whenever there is a change in your Postgres database.

Replies
dillondotzip
Hasura is on 🔥
Alex Barashkov
We migrated one of our project to Hasura. Used it for real time updates for web and mobile apps. Now with this new feature its really possible to do a really cool serverless infrastructure for a very cheap price
Rajoshi Ghosh
@alex_barashkov Hi Alex! That's great news :) We'd love to hear more about what you're building! If you're on our discord server, please do DM @tanmaig or me :)
Rajoshi Ghosh
Hi PH and thank you @kwdinc for hunting us! We’ve made it super easy to capture data changes in a Postgres database and trigger webhooks or serverless functions. This functionality is now available in the open-source Hasura GraphQL engine. Important features: - Atomic and reliable event capture to ensure you never miss an event. - Configure retry logic to prevent transient failures - Implement custom backoff by responding with a “retry-after” header - Redeliver events manually to debug/dev easily - Works with new or existing Postgres databases These are some of the things you can build easily triggered by database changes - Update an algolia search index or a CDN cache - Send an email or push notification - Build asynchronous business logic, like a long-running algorithm or a multi-step workflow I’m especially excited about how well this works with realtime GraphQL (live-queries). The video above is of a food-ordering app that uses only realtime GraphQL to Postgres on the app. All the complex business logic is in serverless functions which the end-user can see as they happen with GraphQL live queries.
Sid Puri
@kwdinc @rajoshighosh hi i wanted to learn more about what was the founding team's hypothesis for the biggest pain point?