September 28th, 2024

Goodbye API. Hello RSQL

rSQL simplifies data access by enabling direct SQL usage, offering features like fine-grained authorization and version control. Currently in beta, it will introduce pricing plans for businesses.

Read original articleLink Icon
Goodbye API. Hello RSQL

rSQL is a new product designed to simplify data access by allowing users to utilize SQL directly across their applications, eliminating the need for REST or GraphQL APIs. It offers features such as fine-grained authorization, version control for data schemas, and secure authentication through JWT and OAuth integrations. rSQL is stateless and can be self-hosted, providing flexibility for developers. The platform is currently in beta and free for use, with plans for a standard pricing model for smaller businesses and variable pricing for larger organizations. The product includes an admin UI for managing queries and authorization, as well as a JavaScript SDK for handling registrations and real-time database changes. While rSQL is not open-source, the team is considering this option for the future. The focus is on providing a powerful, declarative language experience while ensuring ease of use and control for developers.

- rSQL allows direct SQL access, eliminating the need for traditional APIs.

- It features fine-grained authorization and version control for data schemas.

- The platform is currently free in beta, with future pricing plans for different business sizes.

- rSQL can be self-hosted and includes an admin UI and JavaScript SDK.

- The product is not open-source yet, but the team is contemplating this option.

Link Icon 8 comments
By @throaway55623 - 3 months
Creator here.

Not sure how this got into onto HN. Maybe hackandthink can explain.

This product does not actually exist. I wanted to see if there was demand for something like this so I created a landing page for it a few years ago. It only got bad responses. Mostly worries about how authorization rules would work and that it could never be done securely, so I never ended up building it, even though I didn't fully agree with that concern.

I should probably take the page down.

By @parthdesai - 3 months
You've airbnb, coinbase, instgram, dribble, pintrest, and netflix listed there. There are no case studies or documentation about them and these logos themselves aren't clickable.

How are these companies using this technology? Are they using it in prod? Is it in one of their main apps or just an internal tool?

What happens at scale? How do I separate read and write pools? How can I tune query configs and wait times?

By @tuetuopay - 3 months
Is this firebase but from a different vendor and in sql? If so, I'll wait for the security horror stories.
By @jose_zap - 3 months
The screenshot looks like a copy of the hasura web console. The same looks also similar to Hasura’s internal RQL. I wonder if this is just a coincidence.
By @recursivedoubts - 3 months
this completes the move from the server side to the client side

yes, it looks a little crazy and there are certainly serious security considerations (they support ACLs it looks like) but this is the logical end point of JavaScript-based applications that jettison the hypermedia infrastructure of the web

REST (so called, see[1]) was the first step, GraphQL the second step and now this completes the move of pushing the expressiveness found on the server side over to the client side.

[1] - https://htmx.org/essays/how-did-rest-come-to-mean-the-opposi...

By @hexo - 3 months
So, we did full circle, again
By @alphabettsy - 3 months
GraphQL, but SQL.