Goodbye API. Hello RSQL

9 pointsposted 13 hours ago
by hackandthink
(rsql.io)

7 Comments

jose_zap

12 hours ago

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.

parthdesai

12 hours ago

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?

tuetuopay

12 hours ago

Is this firebase but from a different vendor and in sql? If so, I'll wait for the security horror stories.

recursivedoubts

9 hours ago

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...

megadal

6 hours ago

this comment further confirms my belief that GraphQL is a cult.

> this completes the move from the server side to the client side

OK, how does that benefit end users, developers, or administrators? I have never had a person approach me to make a website with a client side database.

> 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.

Again, I don't see the point..? Who does this benefit..? Front-end only devs who want think doing everything on the front end makes a website more modern/app-like..?

Web architectures aren't separated in front end/back end because of technological limitations. We could've been running databases in the browser for decades now. We don't because of Separation of Concerns...

The front end is for presentation tier logic.. the backend is for business logic.

Just because you can do something doesn't mean you _should_, and when something has been possible for a long time but hasn't been done very often, you should ask yourself why that is.

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

How was this article at all relevant to your point..? GraphQL APIs in the wild also 9/10 require API docs (the schema).

Have you ever heard of OpenAPI?

Wait until you find out about JSON:API. Or that you can use OpenAPI with JSON:API.

hexo

12 hours ago

So, we did full circle, again