6 ms·

Postgraphile. Postgres + graphql. It really solves all the negative aspects of graphql. Also, incredibly performant. Their v5 release is also a pretty interesti

Postgraphile. Postgres + graphql. It really solves all the negative aspects of graphql. Also, incredibly performant. Their v5 release is also a pretty interesting piece of tech. https://postgraphile.org/ https://postgraphile.org/

aitchnyu 3y ago
Is there any alternative that works with Python?
nagstler 3y ago
Interesting, This project looks very versatile, Can experiment with quick a backend API on Postgres.
- brycelarkin 3y ago
  It’s one of the few big projects that still feels “open source” as opposed to corporate run open source. I think Netflix is a big user / sponsor of the project.
mdaniel 3y ago
I didn't see a v5 tag in order to know, and I have no idea what "utils/graphile" does for the project, but one will want to ensure they are aware of its licensing scheme https://github.com/graphile/crystal/blob/db8894c74eb0ec3fe960a3f4cad4170004c26519/LICENSE.md#files-under-utilsgraphile-are-not-oss https://github.com/graphile/crystal/blob/db8894c74eb0ec3fe96...
- BenjieGillam 3y ago
  Its an optional command line utility that you may use with PostGraphile which does things like printing out your configuration in a pretty format and using TypeScript to figure out what options are available to you based on the plugins you are using. It is 100% non-essential because all the options are documented in each of the plugins (and also you can use TypeScript auto-complete in your editor), and you can just console.dir() your configuration. You can read about it here: https://postgraphile.org/postgraphile/next/config#viewing-the-available-options https://postgraphile.org/postgraphile/next/config#viewing-th...
igor47 3y ago
Graphile worker is also awesome. Wish celery was as good -- I've been thinking of implementing a compatible worker in Python
grardb 3y ago
I played with this a bit years ago when it was still called PostgraphQL. My biggest issue with it was that there didn't seem to be a recommended (or even suggested) version control method for things like functions. Using a standard migration tool to update functions seems like hell, so I gave up on using it. Looking through the docs, I still see no mention of version control or even migrations at all. Is this something that has been solved?
- brycelarkin 3y ago
  It’d be like any other database schema change. We commit all schema migrations to git and have cicd run them.

aitchnyu 3y ago

Is there any alternative that works with Python?

nagstler 3y ago

Interesting, This project looks very versatile, Can experiment with quick a backend API on Postgres.

brycelarkin 3y ago
It’s one of the few big projects that still feels “open source” as opposed to corporate run open source. I think Netflix is a big user / sponsor of the project.

mdaniel 3y ago

I didn't see a v5 tag in order to know, and I have no idea what "utils/graphile" does for the project, but one will want to ensure they are aware of its licensing scheme https://github.com/graphile/crystal/blob/db8894c74eb0ec3fe960a3f4cad4170004c26519/LICENSE.md#files-under-utilsgraphile-are-not-oss https://github.com/graphile/crystal/blob/db8894c74eb0ec3fe96...

BenjieGillam 3y ago
Its an optional command line utility that you may use with PostGraphile which does things like printing out your configuration in a pretty format and using TypeScript to figure out what options are available to you based on the plugins you are using. It is 100% non-essential because all the options are documented in each of the plugins (and also you can use TypeScript auto-complete in your editor), and you can just console.dir() your configuration. You can read about it here: https://postgraphile.org/postgraphile/next/config#viewing-the-available-options https://postgraphile.org/postgraphile/next/config#viewing-th...

igor47 3y ago

Graphile worker is also awesome. Wish celery was as good -- I've been thinking of implementing a compatible worker in Python

grardb 3y ago

I played with this a bit years ago when it was still called PostgraphQL. My biggest issue with it was that there didn't seem to be a recommended (or even suggested) version control method for things like functions. Using a standard migration tool to update functions seems like hell, so I gave up on using it. Looking through the docs, I still see no mention of version control or even migrations at all. Is this something that has been solved?

brycelarkin 3y ago
It’d be like any other database schema change. We commit all schema migrations to git and have cicd run them.