BenjieGillam

7 ms·

1.
by BenjieGillam 1y ago
Yep; we have a dedicated listener client per pool (and normally something like 1-20 pools, each with 1-100 workers); the workers themselves don’t listen. We also notify on every job or batch job insert, though we would love to rate limit th
2.
by BenjieGillam 3y ago
Completely agree; the issue I see with people who try putting logic in the DB ultimately to reject it is they try and bring their procedural programming paradigms (e.g. “for” loops and “if” statements) into the DB and that’s incredibly inef
3.
by BenjieGillam 3y ago
Yes, currently Node is the runtime but we could bundle that up into a binary blob if that would help; one thing to download rather than installing Node and all its dependencies? A UI is a common request, something I’ve been considering inve
4.
by BenjieGillam 3y ago
Not sure if you saw it but Graphile Worker supports jobs written in arbitrary languages so long as your OS can execute them: https://worker.graphile.org/docs/tasks#loading-executable-fi... Would be interested to know w
5.
by 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
6.
by BenjieGillam 3y ago
You can use absolutely any migration framework you like with PostGraphile, it’s completely unopinionated about that.
7.
by BenjieGillam 3y ago
You have to get used to mentioning it in every available avenue (readmes, docs, CLI greeting message, any web UIs, release notes, issue templates, etc), and also be happy with a really slow ramp-up time, but yes, it’s possible. Source: I’m
8.
by BenjieGillam 5y ago
Graphile Worker maintainer here; keep in mind that postgres is not the ideal location for a job queue, so you’re going to be limited ultimately by postgres’ capabilities. I’ve seen Worker max out at around 10k jobs/second but very much
9.
by BenjieGillam 5y ago
> Postgraphile, et al. all seem to suggest that you should stand up a separate service for this. PostGraphile maintainer here; with the exception of recommending job queues for work that can/should be completed asynchronously (which
10.
by BenjieGillam 5y ago
That's not true; you can use row level security (RLS) to control access (both reading and writing) on a per-row basis. You can think of it as similar to an implicit "where" clause that automatically gets added to all requests
11.
by BenjieGillam 5y ago
Most PostGraphile projects have two or three PostgreSQL roles total, and that can support millions of application users. This is such a common misconception that we created an infosheet about it: https://learn.graphile.org/d
12.
by BenjieGillam 5y ago
Or use an API layer such as GraphQL that doesn’t require versioning for such a minor change since additive changes (or deprecations) to the API do not affect existing queries - each query states exactly what it needs.
13.
by BenjieGillam 5y ago
Please note you can add custom handlers in PostGraphile using JS as well as SQL; we have an extensive plugin API, but if you just want to use SDL and resolvers we’ve a plugin generator for that: https://www.graphile.org/post
14.
by BenjieGillam 6y ago
Apparently you can’t reply with just emoji here, so: _high five emoji_
15.
by BenjieGillam 6y ago
Graphile Starter-based stack (Node, PostGraphile, Next.js, Graphile Worker) running on Heroku with Amazon RDS Postgres. Virtually no server maintenance needed: just push the code to GitHub, check it works on staging, press the promote to pr
16.
by BenjieGillam 6y ago
PostGraphile is designed for a situation where Postgres is your main data store, and other things are ancilliary. You can add in the other things with traditional GraphQL resolvers via the plugins/etc that you've mentioned; but if
17.
by BenjieGillam 6y ago
Thanks! Makes sense; best of luck with your future projects!
18.
by BenjieGillam 6y ago
Out of interest (as the PostGraphile maintainer) did you look into https://www.graphile.org/postgraphile/make-extend-schema-plu... for extending the PostGraphile schema to do whatever you need, or were you specifically
19.
by BenjieGillam 6y ago
[PostGraphile author here, and I wrote that page of documentation.] Firstly, GraphQL does not allow for infinite recursion; it is literally not possible to do infinite recursion in GraphQL; the GraphQL spec even has a section on this: http
20.
by BenjieGillam 6y ago
I’m the maintainer of PostGraphile and I also don’t approve of “just expose your database to the world and let your frontend just get whatever data it needs.” PostGraphile is a tool to help you to rapidly build performant and secure GraphQL
21.
by BenjieGillam 6y ago
<checks the income from the pro plugin versus that from sponsorship> I can definitely confirm that we're significantly more personal/community driven than commercial.
22.
by BenjieGillam 6y ago
No worries, I think judging things we're unfamiliar with is very human - it's necessary to protect our own time because we can't afford to research _everything_. We just need to be careful to not share these quick judgements
23.
by BenjieGillam 6y ago
PostGraphile maintainer here; what you’ve said is not really true for PostGraphile - we give you a huge toolbox of ways to customize, shape and extend your schema so it’s designed for consumers to consume rather than just being a way of exp
24.
by BenjieGillam 7y ago
This absolutely isn't required; I think you might be getting confused with RBAC rather than RLS. Handy infosheet: https://learn.graphile.org/docs/PostgreSQL_Row_Level_Securit...
25.
by BenjieGillam 7y ago
“While we will discuss how you can use the schema we create with PostGraphile, this article should be useful for anyone designing a Postgres schema.”
26.
by BenjieGillam 7y ago
Agreed: an API that _just_ maps to CRUD operations isn’t good. I’m not advocating for that, neither is singingwolfboy, and the starter repo he’s linked to basically does not use them: there are only 4 CRUD mutations, all the others are cus
27.
by BenjieGillam 7y ago
Absolutely not, this is a common misconception. Have a read of this: https://learn.graphile.org/docs/PostgreSQL_Row_Level_Securit...
28.
by BenjieGillam 7y ago
It's not generally safe to expose SQL to untrusted clients. For example, PostgreSQL 12.2 was released yesterday and fixed a security issue where `ALTER ... DEPENDS ON EXTENSION` did not have any privilege check whatsoever. SQL is also
29.
by BenjieGillam 7y ago
Check out Graphile Starter; it’s extremely batteries included! https://github.com/graphile/starter
30.
by BenjieGillam 7y ago
Check out Graphile Starter; it is a fullstack starter project for building a SaaS with PostGraphile in TypeScript with React (Next.js) and Apollo Client. It has all of the modern tooling preconfigured including type checking, linting, forma

More ›