Hasura VS Flamelink.io

> 2. ORMs do not hide SQL nastiness. This is certainly true! I mean: ORMs are now well known to "make the easy queries slightly more easy, while making intermediate queries really hard and complex queries impossible". I think the are of ORMs is over. It simply did not deliver. If a book on SQL is --say-- 100 pages, a book on Hibernate is 400 pages. So much to learn just to make the easy queries slightly easier to... - Source: Hacker News / 5 days ago

Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically. - Source: dev.to / 29 days ago

Today, this ecosystem is going strong with new providers like Hasura, AppWrite and Supabase powering millions of projects. There are a few reasons people choose this style of hosting, especially if they are more comfortable with frontend development. BaaS lets them set up a database in a secure way, expose some business logic on top of the data, and connect via a dev-friendly SDK from their app or website code to... - Source: dev.to / 2 months ago

Hi! If you’ve ever thought about something like using GraphQL for something like this.. You might like Hasura. (Obligatory I work for Hasura) We’ve got an OpenAPI import and you can setup cron-jobs or one-off jobs and do things like load in headers from the environment variables to pass through. There isn’t currently an easy journey for chaining multiple calls together without writing any code at all, but you can... - Source: Hacker News / 2 months ago

Hasura.io — Hasura extends your existing databases wherever it is hosted and provides an instant GraphQL API that can be securely accessed for web, mobile, and data integration workloads. Free for 1GB/month of data pass-through. - Source: dev.to / 3 months ago

You also have https://flamelink.io/. Source: over 2 years ago

I've looked at PushTable and FlameLink already, but PushTable didn't seem to work at all, and FlameLink is really out of the budget for a small site like this. Source: over 2 years ago

I'm not sure I'd say Firestore is the ideal "serverless" backend for a Svelte app, but it sure does make it easier to develop and iterate faster. Plus with Flamelink it's provided a decent solution for use with a full-blown non-technical CMS system that we didn't have to build. Flamelink offers some primitive relational db style functionality (e.g. Some document fields can be references to other documents) which... Source: almost 3 years ago

We've gone with Firebase for our "backend" needs. This is primarily just firestore for data, cloud-functions for database sanitization, auth, and basic usability analytics. We're using it in conjunction with a CMS service called Flamelink that allows the non-technical folks on our team to add content to firebase in reasonably intuitive way without us needing to build/maintain a second app just for... Source: almost 3 years ago

The main draw of any CMS is that it lets authorized users customize content without having any knowledge of how to code. If someone knows how to use a text editor, then they should be able to create new content using the CMS. I’m going to teach you how to set up Firebase and add Flamelink to your Angular application. You’ll have it up and running in short order! - Source: dev.to / over 3 years ago