From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
---|---|
To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: RPC via WebSockets. |
Date: | 2020-01-18 02:54:06 |
Message-ID: | CANNMO+JpA8GqUosJMuEgdKeCovCQ0ou2OwuOf9jrMqus4pFGdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This is a very common task, definitely.
As for WebSockets, there is an addition to PostgREST, postgrest-websockets
https://github.com/diogob/postgres-websockets#readme
PostgREST is not only for "give me contents", you can write functions (in
any PL) and call them using POST /rpc/functionname.
There is also an attempt to build similar tool in Go (although I'm not sure
how popular and powerful it is): pREST https://github.com/prest/prest
Finally, there is a whole line of trendy and quite popular tools for having
GraphQL on top of Postgres, including but not limited to:
- PostGraphile https://github.com/graphile/postgraphile
- Hasura https://github.com/hasura/graphql-engine
- Prisma https://github.com/prisma/prisma
On Fri, Jan 17, 2020 at 13:18 Dmitry Igrishin <dmitigr(at)gmail(dot)com> wrote:
> Hello!
>
> Who needs to talk to Postgres right from a WEB-browser via WebSockets? For
> example, conveniently call storable functions/procedures?
>
> Yes, i know about PostgREST. But I want to focus on RPC via WebSockets
> without all these REST or "give me contents of that table by this URL"
> stuff...
>
> I'm thinking about writing an application which is simple to
> install/deploy, simple to configure, with a connection pool built-in.
> Ideally, one binary and one config in JSON format.
>
> I need some feedback before start. So please don't hesitate to share any
> of your thoughts/ideas/comments/scepticism here :-)
>
> Thanks.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Igrishin | 2020-01-18 05:36:34 | Re: RPC via WebSockets. |
Previous Message | Rob Sargent | 2020-01-17 23:30:59 | Re: jsonb_set() strictness considered harmful to data |