magic VS Hasura

As an additional bonus, it completely eliminates all Postman script kiddies, since the client must be able to execute code to create a valid token. It also eliminates reusing the same token for multiple servers, since each server has their own unique public key - In addition to that you get to market your AI chatbot as "powered by Blockchain technology", and you can actually say that out loud with a straight face, without lying ... 🤪

As an AI chatbot provider, we need some serious bot protection to prevent malicious users from creating bots that attacks us. Google reCAPTCHA of course is "the industry standard" here, which I'm sure most readers are aware of.

I just swapped out Google Analytics with Plausible for AINIRO.IO. It’s only been a week, but so far I am super jazzed about it. First of all, Plausible doesn’t use cookies, so I can completely drop all cookie disclaimers and popups I had because of GDPR. Second of all, the site scores significantly better on load time. This results in a 10x better user experience for my website visitors, while making sure the website is still 100% conforming to GDPR laws.

After having owned an AI chatbot company for more than a year, I finally did what I'm supposed to do before I even start a company; I did a Competitor analysis - And o'boy should I have done it earlier.

We've got an AI chatbot for instance. On every single neutral parameter it's 10,000 times better than 99.99% of everything else out there. However, at ProductHunt you will have to go to "page 11,670" before you'll find our AI chatbot.

In addition I've got zero contributions to my primary projects. Some guy contributed to Lizzie a couple of years ago, but my primary project has zero contributions. Notice, I happen to know for a fact that there are a whole range of really, really, really rich companies using Magic for instance, some of whom are cashing in millions of dollars in profit every single year.

In addition Magic Cloud has now become a real business model, with a quite substantial amount of revenue, through our AI and Low-Code hosting provider. So to avoid having leeches exploiting our work for free without contributing in any ways, it's therefor with heavy heart we announce that all future releases of Magic will be in the form of closed source distributions.

I have an open source project myself, and I am building an AI and Low-Code/No-Code platform company on top of it. Contrary to SupaBase though, I have spent 4 years creating real value in my platform. The project solves a real problem, it consists of a lot of real innovations, and I’ve spent a lot of time building it.

Warning - This is not going to make any sense for anyone reading this, including me, so I won't try to make any sense of it - I'll let the reader interpret it in whatever way the reader wants to interpret it. However, when you're building an open source platform, such as our Magic Clouc, the first thing investors will ask you about is how many users you have.

When the article was published, it rapidly broke all records, and became the 5th most read article Microsoft had ever published. Today the article is a bit dated, and if you're interested in learning Hyperlambda, you're much better off reading its official documentation.

[4] https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md

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.

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 save data easily. These modern tools build a blend of managed database with curated plugins such as authentication, great admin dashboards, and function as a service type capability - all in one package, and often offered as a integrated hosted service.

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 wrap pretty much any API endpoint via OpenAPI import or a custom action, and you can even make minor edits to things like the API contract format to change aliases/naming.

Our goal is to join all the things, databases and API’s. Most people know us for instant GraphQL API’s that give you CRUD on your database, but we also wrap APIs.

Not sure if something like this would fit your use-case and do check out some of the other things mentioned, but depending what you are trying to do I think Hasura might potentially work.

You can find out more here: https://hasura.io

Nested Mutation - 113 thumbs up, and still open since 2019... another case of not listening to the users?

Hasura is an open-source real-time GraphQL API server with a strong authorization layer on your database. You can subscribe to database events via webhooks. It can combine multiple API servers into one unified graphQL API. Hasura is a great tool to build any CRUD GraphQL API. Hasura does not have any authentication mechanisms; e.g., you need an auth server to handle sign-up and sign-in.

7. Hasura