Viewing profile — BenjieGillam

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 jo…

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…

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 …

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-executab…

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…

You can use absolutely any migration framework you like with PostGraphile, it’s completely unopinionated about that.

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 re…

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…

> 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 wor…

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 …

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 info…

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 - eac…

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 gener…

Apparently you can’t reply with just emoji here, so: _high five emoji_

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 t…

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…

Thanks! Makes sense; best of luck with your future projects!

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 whate…

[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…

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 too…

I can definitely confirm that we're significantly more personal/community driven than commercial.

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…

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 …

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...

“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.”