Show HN: Rest – Instant RESTful API on Any SQL Database • Hacker News Board

Generally been a fan of these sorts of models - SQL data is very malleable - and treating the tables as movable from the start really helps move faster as a developer - database migrations become easier as you don't need to do a lot of work with API.

I can see how this would cause problems if you always used this in production after finding a fit for the data model - but for rapid prototyping and development - big fan.

Re: Show HN: Rest – Instant RESTful API on Any SQL Database

#9

Post by SOLAR_FIELDS » Fri, Jan 27, 2023, 2:17 AM UTC

varunsharma07 wrote: post #6

It would be great if it could support NoSQL databases as well. I use DynamoDb as an example, and I had to write REST APIs myself.

Yes it would be great. But this is kind of like saying people who have a pattern for making quilts should use their techniques to get into the sheet business. On the surface it makes sense, but when you dig into the details it turns out that the way you make quilts and the way you make sheets are so fundamentally different it’s not even worth exploring a common ground. Yes we both make things that go on peoples beds, but the manufacturing internals are so completely different that it’s not even worth having the conversation about how they could be married.

Re: Show HN: Rest – Instant RESTful API on Any SQL Database

#10

Post by shellfly » Fri, Jan 27, 2023, 4:09 AM UTC

dantetheinferno wrote: post #8

Pretty cool - wonder how it compares to Postgrest ( https://postgrest.org/ ). Generally been a fan of these sorts of models - SQL data is very malleable - and treating the tables as movable from the start really helps move faster as a developer - database migrations become easier as you don't need to do a lot of work with API. I can see how this would cause problems if you always used this in production after finding…

The original idea was inspired by PostgREST, the obvious difference is Rest tries to support all SQL databases, and it results in some design principle that Rest prefers to use a universal method instead of bind to PG features(e.g. use PG role for user authorization). Generally PostgREST is more mature now if you are using PG. Thanks for liking it, I also think it could be a good tool to help developers for rapid prototyping and development.