Our great sponsors
-
-
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 a fit for the data model - but for rapid prototyping and development - big fan.
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
Related posts
- What are the advantages of using Rust to develop KV databases?
- is it a good idea to develop a database with direct rest API access??
- How to use Supabase RLS with third-party client library?
- Ask HN: How do you test SQL?
- I would like to know your advice, I am creating an inventory control software, and I would like to use the PostgreSQL database instead of SQL Server, Could you give me your opinions of the advantages and disadvantages of using one or the other, Thank you.