graphql VS postgres-websockets

Compare graphql vs postgres-websockets and see what are their differences.

graphql

Haskell GraphQL implementation (by jdnavarro)

postgres-websockets

PostgreSQL + Websockets (by diogob)
Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SaaSHub - Software Alternatives and Reviews
graphql postgres-websockets
0 1
167 303
- -
0.0 4.1
over 3 years ago about 1 month ago
Haskell Haskell
BSD 1-Clause License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

graphql

Posts with mentions or reviews of graphql. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning graphql yet.
Tracking mentions began in Dec 2020.

postgres-websockets

Posts with mentions or reviews of postgres-websockets. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-29.
  • PostgREST – Serve a RESTful API from Any Postgres Database
    22 projects | news.ycombinator.com | 29 Dec 2022
    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?

When comparing graphql and postgres-websockets you can also consider the following projects:

postgrest - REST API for any Postgres database

async-ajax - Haskell: Cross browser AJAX Bindings for GHCJS

yesod-persistent - A RESTful Haskell web framework built on WAI.

servant - Main repository for the servant libraries — DSL for describing, serving, querying, mocking, documenting web applications and more!

swagger2 - Swagger 2.0 data model.

graphql-api - Write type-safe GraphQL services in Haskell

swagger-petstore - swagger-codegen contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition.

servant-purescript - Translate servant API to purescript code, with the help of purescript-bridge.

socketio - socket.io for haskell folks

yaml - Support for serialising Haskell to and from Yaml.

gc-monitoring-wai - a wai application to show `GHC.Stats.GCStats`