postgrest-starter-kit
postgres-websockets
postgrest-starter-kit | postgres-websockets | |
---|---|---|
3 | 1 | |
710 | 338 | |
- | - | |
0.0 | 7.2 | |
about 3 years ago | 6 months ago | |
PLpgSQL | Haskell | |
MIT License | BSD 3-clause "New" or "Revised" License |
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-starter-kit
- Starter Kit and tooling for authoring REST API back ends for PostgREST
-
PostgREST – Serve a RESTful API from Any Postgres Database
I think the recommended way to use Postgrest is to put a layer of views and optionally stored functions on top of your schema to decouple it from your API. Take a look at this Postgrest starter kit[1] which uses a separate API schema for this purpose.
[1] https://github.com/subzerocloud/postgrest-starter-kit
- Auto generating API schema code?
postgres-websockets
-
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...
[4] https://github.com/PostgREST/postgrest/issues/2530
What are some alternatives?
sqlx - general purpose extensions to golang's database/sql
postgrest - REST API for any Postgres database
graphile-engine - Monorepo home of graphile-build, graphile-build-pg, graphile-utils, postgraphile-core and graphql-parse-resolve-info. Build a high-performance easily-extensible GraphQL schema by combining plugins!
graphql-api - Write type-safe GraphQL services in Haskell
seafowl - Analytical database for data-driven Web applications 🪶
graphql - Haskell GraphQL implementation
pocketbase - Open Source realtime backend in 1 file
gc-monitoring-wai - a wai application to show `GHC.Stats.GCStats`
subzero-starter-kit - Starter Kit and tooling for authoring GraphQL/REST API backends with subZero
raml - RESTful API Modeling Language (RAML) library for Haskell
annuaire-entreprises-sirene-api
simpleconfig