I’m using Hasura for the first time for my current startup, and it’s been a game changer for speed so far. What I’m loving most about it is how is changes the

I’m using Hasura for the first time for my current startup, and it’s been a game changer for speed so far. What I’m loving most about it is how is changes the team schedule. Let me explain. Usually, we’d prototype out what we wanted to build, verify with users, then create the overall data models. For every single new feature, we’d create API endpoints (REST or GraphQL) and then the front-end. With Hasura (or Supabase or Firebase for that matter), we skip the API step for _most_ pages. If a page can be built 100% using CRUD operations, it’s a awesome! If a page can’t be done this way (lots of multi-table transactions, TensorFlow, background processing needed), we hand it off to our Express.js app either through Hasura triggers or federated GraphQL to handle it. In that case, the amount of work to do is the same as if we weren’t using Hasura. After 13 years of Ruby on Rails development this has been a major change in how I build apps - but one I’m excited about. I wrote up a post detailing more about why I’m making the switch on my startups blog too if you’re curious: https://hardcover.app/blog/the-perfect-startup-tech-stack https://hardcover.app/blog/the-perfect-startup-tech-stack