postgrest
supabase
Our great sponsors
postgrest | supabase | |
---|---|---|
76 | 597 | |
20,236 | 47,460 | |
1.4% | 5.5% | |
8.7 | 10.0 | |
7 days ago | about 7 hours ago | |
Haskell | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgrest
- is it a good idea to develop a database with direct rest API access??
-
Is a custom CMS a bad idea?
wait till you find out https://github.com/PostgREST/postgrest.
-
How to use Supabase RLS with third-party client library?
Yes that's exactly what I'm reading here and there. It seems to be the approach that Supabase is taking itself when receiving queries via their API gateway, powered by PostgREST. I had a look at the source code for the latter and it's basically converting the claims in the received JWT into as many local set_config() calls (basically a wrapper function around SET LOCAL). See this related discussion.
-
Can't link fresh project - problem with underlying postgrest version not supporting 15.
I suspect this is the culprit (might be wrong): https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/Config/PgVersion.hs
-
Show HN: Rest – Instant RESTful API on Any SQL Database
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.
-
Architecture Pitfalls: Don’t use your ORM entities for everything — embrace the SQL!
Just as an addendum, the supabase.com team are bullish on the power and value of leaning heavily into the database. iirc, they're also the team behind postgREST which makes it easy to spin up a full REST API on the back of a PostgREST database. I used to think this kind of approach was a disaster, but I've changed my mind significantly. When being willing to use stored procedures, you can spin up this REST API, AND use the same stored procedures for your application as well, to ensure consistency of business logic, all without needing a separate business logic API middleware service between DB and the rest of the world. It's not all roses, but it is pretty amazing.
-
PostgREST – Serve a RESTful API from Any Postgres Database
At work, we've finally replaced a large part of a custom (mostly-)web backend with PostgREST recently, and that's quite a relief: considerably less code to maintain in that project now, and that was a rather awkward code. Something akin to PostgREST's "Embedding with Top-level Filtering" [1] had to be provided for all the tables, with OpenAPI schema and a typed API (Haskell + Servant); I avoided manually writing it all down, but at the cost of poking framework internals, and maintainability suffered. It was particularly annoying that the code doesn't really do anything useful, except for standing between a database and an HTTP client, and simply mimics the database anyway. Whenever a change had to be introduced, it was introduced into the database, the backend, and the frontend simultaneously, so it wasn't even useful for some kind of compatibility.
Now PostgREST handles all that, and only a few less trivial endpoints are handled by a custom backend (including streaming, which I'm considering replacing with postgrest-websocket [2] at some point).
During the switch to PostgREST, the encountered minor issues were those with inherited tables (had to set a bunch of computed/virtual columns [3] in order to "embed" those), and with a bug on filtering using such relations (turned out it was an already-fixed regression [4], so an update helped). Also a couple of helper stored procedures (to use via /rpc/) for updates in multiple tables at once (many-to-many relationships, to edit entities along with their relationships, using fewer requests) were added (though the old custom backend didn't have that), the security policies were set from the beginning, the frontend was rewritten (which allowed to finally switch without adding more work), so it was only left to cleanup the backend.
Not using views, since as mentioned above, database changes usually correspond to frontend changes, and the API doesn't have to be that stable yet.
Happy with it so far.
[1] https://postgrest.org/en/stable/api.html#embedding-with-top-...
[2] https://github.com/diogob/postgres-websockets
[3] https://postgrest.org/en/stable/api.html#computed-virtual-co...
For how often Nix is mentioned here on HackerNews, has anybody looked at the Nix config files for this repo to build it locally?
https://github.com/PostgREST/postgrest/blob/main/cabal.proje...
-
Looking for a boilerplate
I don't know for the stack you're looking for but is this close enough ? https://github.com/PostgREST/postgrest
-
Should I replace all db select query REST APIs with a single generic router ?
It's neither MySQL nor Go, but https://github.com/PostgREST/postgrest has figured out most of the patterns and API designs you could follow.
supabase
-
10 open-source alternatives to run your businesses
5. Supabase - 47.4k ⭐️
-
Why is supabase dev experience so terrible?
See https://github.com/supabase/supabase/blob/master/examples/slack-clone/nextjs-slack-clone/README.md - has multiple roles.
-
General considerations for SQLite as the database for production environment
I personally would go DBaaS every day. If you don't want to use AWS or Google Cloud, you could checkout Supabase or Pocketbase and see how you can host them locally for your requirements.
-
Roll for your kingdom: First experiment with svelte
Besides svelte/sveltekit, it uses Zod and tRCP connected to a Supabase postgres database via Prisma and deployed on vercel.
-
Create a blog with supabase and nextjs - part 1
In this tutorial, we will build a simple blogging application using Next.js and Supabase. Next.js is a popular React framework for building server-side rendered and statically generated web applications, while Supabase is an open source Firebase alternative that provides a PostgreSQL database and authentication APIs out of the box. By combining these technologies, we can easily create a performant and scalable blogging platform.
-
Multi-tenant implementation approaches with Prisma and ZenStack
Advanced If you are using Postgres as your database or a service provider that is based on it, such as Supabase, you have the advantage of utilizing the advanced feature of RLS (Row Level Security) provided by the database. This way, defining role-based access policies in the database becomes the primary task to control which rows of data can be accessed.
-
My Favorite Free Hosting Services of 2023
Supabase
-
Building a full-stack app for learning Italian: Supabase vs. Wasp
I showed it to my girlfriend, but she didn't like some of the phrases I used. If only I had a backend with a database to edit the phrases. Then I had an idea: let's add a database with Supabase.
-
CheatGPT is Here: Upgrade Your Chat Experience
CheatGPT is built using the latest web technologies, including SvelteKit, Tailwind, DaisyUI, Supabase, and Vercel. We've chosen these technologies for their speed, efficiency, and ease of use, and we're confident that they'll provide a great user experience for everyone who uses CheatGPT.
-
HEROKU ALTERNATIVES TO HOST SERVER AND DB.
Netlify doesn't have a db service, so you'll have to host that somewhere else. maybe try Supabase. https://supabase.com/
What are some alternatives?
Appwrite - Secure Backend Server for Web, Mobile & Flutter Developers 🚀 AKA the 100% open-source Firebase alternative.
nhost - The Open Source Firebase Alternative with GraphQL.
pocketbase - Open Source realtime backend in 1 file
next-auth - Authentication for the Web.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
Directus - The Modern Data Stack 🐰 — Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
faunadb-js - Javascript driver for FaunaDB
vitess - Vitess is a database clustering system for horizontal scaling of MySQL.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
php - 🐘 PHP Runtime for ▲ Vercel Serverless Functions
mongo-parse - A parser for mongo db queries and projections.