V5's database queries are much simpler and more performant than in V4 (which was already faster than traditional execution methods!) thanks to offloading work from Postgres to the Grafast planning engine in Node. I'm so happy that what started out as a theory is now having such measurable impact!
Thank you for sharing your finding! This is such great news!
One of the key goals of PostGraphile V5 was to increase scalability by offloading work from the database to the JS layer; we are thrilled to hear that this goal is already having a significant positive impact!
It would be hard to understate how large of a feat of engineering this was. PostGraphile is such a powerful tool and it's great to see such a great foundation for the future in v5
Kudos to @benjie.dev, Jem, and all who contributed to Postgraphile
Thanks for the kind words, Paul - and of course for your work in ReScript! We've quite a few in the community that use it from what I hear in the chat, and never a bad word spoken!
I've been using postgraphile for years at work, including latest V5 RCs and it's just a pure gem, very fast and extremely flexible, plus it works perfectly with rescript-relay! Kudos @benjie.dev for the great work!
PostGraphile V5 is here!
New execution engine.
New export system.
New extension capabilities.
Same focus on productivity and performance!
This is the biggest release we’ve ever shipped.
See what changed: postgraphile.org/news/2026-0...
GraphQL error handling sucks. There, I said it.
Null checks everywhere, and ambiguity: error, or true null? We've all been there.
In this talk, Benjie Gillam shows how to fix GraphQL's biggest mistake in 512 bytes. 👇
youtu.be/odwQUAkmW44
Selfie of Benjie and Jem
Hi #GraphQLConf! We are on floor 2 doing “man on the street” small interviews about how your conference has been going, if you want to share a key takeaway or favourite talk come and find us!
Our team is at #GraphQLConf today, if you’re here come and say hi! It was a blast to celebrate the GraphQL Stars on stage and launch the Ambassador Program
New Release! We reckon we're about 90% of the way to Grafast 1.0 and PostGraphile 5.0 release candidate stage 🥳
www.graphile.org/news/2025060...
And finally, it's got to be durable so there's a daily job that checks for due recurring expenses then queues up a task to create each expense
@graphile.org Worker has been great for this!
GraphQL London is always a hit. Make sure to check it out if you're around!
We are looking for a second speaker for @london-graphql.bsky.social on 1st July, new and seasoned speakers most welcome!
📣 Calling All GraphQL Experts!
Be a part of shaping an epic GraphQLConf - help us choose the most impactful talks!
🎉 Details here: graphql.org/blog/2025-0...
graphql-sock v1.0.0 CLI & library now available on npm; converts a schema with semantic nullability (eg via `@semanticNonNull` directives) to traditional syntax for compatibility with existing tooling (eg codegen).
Pairs great with graphql-toe — throw on read from an errored field.
Blog post soon!
🪅 Apr 29th at 6PM: London GraphQL April
London GraphQL will be held on July 5th at Herbal House, 8-10 Back Hill, London EC1R 5EN. Two talks on the most up-to-date GraphQL topics interspersed with pizza.
Check it out 👉 https://guild.host/e/fl322c
"Three maintainers talk about how they fostered their open source communities." Including me! It's been a brilliant experience building our @graphile.org community over the last 7 years.
Who do you want to see on the Amsterdam stage in September? Give them a nudge, and let us know!
⭐️ Yaacov isn't just a #graphqlstar, he's a constellation! Thank you for being a driving force behind graphql.js, the Spec, and the incremental delivery directives ❤️
At #FOSDEM? We’re here in Building K (lvl 4) for the APIs devroom, a good mixture of GraphQL, OpenAPI and AsyncAPI fosdem.org/2025/schedul...
At #FOSDEM? You have one hour left to find the #GraphQL Stand in Building H, there’s still some stickers left! Or catch us tomorrow in building K for the API’s devroom 😁
Graphile heart stickers
GraphQL stickers
We are here at #FOSDEM and wow! What a difference four years made. When we were last here in 2020 almost no one had heard of GraphQL, but now people are excited to talk about it and love it so much!
Real talk though, you should be using trusted documents (persisted operations)!
Don’t be caught off guard by untrusted operations on your GraphQL API and use HTTP get reliably!
Benjie is sat at a stand with lots of stickers and cheatsheets about GraphQL and Graphile projects
We’ve made it to #FOSDEM! Come and find us in building H, talking about PostGraphile, Grafast and @graphql.org
Hello to our new followers! We are Graphile, the team behind Grafast, PostGraphile and Graphile Worker. MIT open-sourced developer tooling for GraphQL, Postgres & Node, supported by sponsorship from the community, see our projects here: github.com/graphile
I know most software engineers hate writing docs, but I've always kinda loved it. I've really enjoyed contributing to the @graphile.org docs over the last couple weeks on the side.
Turns out that contributing docs to OSS projects isn't so hard 🙂
#GraphQL starter pack
bsky.app/starter-pack...
Today we came across floss.fund/blog/announc...
An initiative from zerodha.tech to fund up to $1M/yr into open source. It's so great to see more companies realise they need to fund the free software they rely on.
With @opensourcepledge.com making headlines recently, the future is looking bright!
