WOwosos·Oct 22, 2017Submission
PostgREST Starter Kit – Full Rest API Over Postgres
2 points · Open discussionsubzerocloud
postgrest-starter-kit
PLpgSQL2017–2023
subzerocloud / postgrest-starter-kit · Archived
postgrest-starter-kit
Starter Kit and tooling for authoring REST API backends with PostgREST
6Distinct people
18Mentions
0Explicit recommenders
744GitHub stars
What to know before exploring
What it is
Starter Kit and tooling for authoring REST API backends with PostgREST
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2017-05-16 12:54:36 UTC to 2023-06-16 06:15:30 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 9 | 2 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
9 sourcesyou don't create a database user for every web user (unless maybe if you have like only 5-10 webusers in total).
you use the user_id from the jwt tokens in your RLS policies and view definitions.
More details here https://github.com/subzerocloud/postgrest-starter-kit/wiki/A...
In Stop calling PostgREST “MAGIC”It's a lib working at a higher level so things like n+1 are left to be solved by the user since the implementation details depend very much on the underlying data storage.
If you use PostgreSQL however, i solve that problem :) https://subzero.cloud (GraphQL & REST api for your database)
It's still in private beta but you can get a sense of how things are put together by looking a this OS project (just REST) https://github.com/subzerocloud/postgrest-starter-kit
In Apollo Server 1.0 – GraphQL Server for Node.js Frameworksyou can if you really want to, but you are not supposed to.
this tool gives you a way to talk to your database, not other systems. to talk to 3rd party systems you use other components in the stack (openresty/rabbitmq)
https://github.com/subzerocloud/postgrest-starter-kit
In How to GraphQL – A Fullstack Tutorial for GraphQLworking on a coherent way here https://github.com/subzerocloud/postgrest-starter-kit/wiki
writing docs is hard but what do you expect :), GraphQL is FB funded, PostgREST is 3-4 guys, no backing.
In How to GraphQL – A Fullstack Tutorial for GraphQLI bet they ar doing exactly that, exposing the api supported by PostgREST :)
https://github.com/subzerocloud/postgrest-starter-kit/wiki/P...
Edit: seems they are not, ... oh well :)
In How to GraphQL – A Fullstack Tutorial for GraphQLThis tool enables a decoupled architecture.
A simple example is sending emails when a user signs up. Instead of having explicit code in your signup function that does the work (and slows down your response), you just have to worry about inserting the row into the database. After this, a database trigger will generate an event which gets sent to RabbitMQ. From there, you can have multiple consumers reacting to that event (email, sms, log, cache).
Those consumers tend to be very short, self contained scripts.
A more complex example is if you pair pg-amqp-bridge and the Web STOMP plugin for RabbitMQ, you can enable flexible and robust real time updates with almost zero code for your frontend.
The larger goal is to enable the development of backends around PostgREST [1] / subZero [2] philosophy. Check out the PostgREST Starter Kit [3] to see
Read the rest
how pg-amqp-bridge fits in a larger project.
Similar work (for kafka) is bottledwater-pg [4] which has a nice blog post [5] explaining the benefits of the architecture
[1] https://github.com/begriffs/postgrest
[2] https://subzero.cloud
[3] https://github.com/subzerocloud/postgrest-starter-kit
[4] https://github.com/confluentinc/bottledwater-pg
[5] https://www.confluent.io/blog/bottled-water-real-time-integr...
For your next PostgREST based project you might want to try
https://github.com/subzerocloud/postgrest-starter-kit with the aid of https://github.com/subzerocloud/devtools
In Visualizing Uber and Lyft trips in San Francisco: more than 200K trips a dayShow HN: PostgREST Starter Kit – Boilerplate and Tooling for Authoring REST APIs
7 points · Open discussion