Success!
✅ @ash-hq.org Serving GraphQL
✅ @solidjs.com app with GraphQL Primitives library
✅ Query + resolving data with simple types to show a simple list.
Next: Ash TypeScript - unsure it can serve types to a different repo/separate front-end though 🤔j
✅ @ash-hq.org Serving GraphQL
✅ @solidjs.com app with GraphQL Primitives library
✅ Query + resolving data with simple types to show a simple list.
Next: Ash TypeScript - unsure it can serve types to a different repo/separate front-end though 🤔j
October 31, 2025 at 12:51 AM
Everybody can reply
2 likes
GraphQL isn't REST's competitor. It's SQL for your APIs.
Apollo's CEO explains why this matters more than you think.
www.youtube.com/watch?v=Z0Ce...
Apollo's CEO explains why this matters more than you think.
www.youtube.com/watch?v=Z0Ce...
October 30, 2025 at 10:03 PM
Everybody can reply
1 likes
Addendum: are there other statically analyzable ways to express parameters that might have the same properties, without the cruft of GraphQL? Yeah! You can do that.
- Runtime data masking might be harder to achieve, but you can certainly imagine having many of the benefits of GraphQL as follows:
- Runtime data masking might be harder to achieve, but you can certainly imagine having many of the benefits of GraphQL as follows:
October 30, 2025 at 8:57 PM
Everybody can reply
have data masking and colocation, which IMO is the only reason to use GraphQL to build UIs. Everything else (the shit type system, idiotic restrictions left and right like not being able to have interfaces with no fields, the lack of sealed unions/interfaces, etc. is a price to put up with to get
October 30, 2025 at 8:57 PM
Everybody can reply
accepted by your framework/GraphQL compiler of choice. But it's also ugly and hard to reason about. So in cases like that, the thing you may want to do is to spread and use a common fragment.
- But realistically, I don't think anyone is thinking at that level. Instead, they think of DevEx
- But realistically, I don't think anyone is thinking at that level. Instead, they think of DevEx
October 30, 2025 at 8:57 PM
Everybody can reply
to `fooGraphQL(ref) {const data = useFragment(graphql` fragment Foo on User { name }`, ref)`
- These are input types that are explicitly, easily statically analyzable! c.f. `fooNonGraphQL(data: SomeType)`, which is not easily statically analyzable
- So, why would you reuse a parameter type
- These are input types that are explicitly, easily statically analyzable! c.f. `fooNonGraphQL(data: SomeType)`, which is not easily statically analyzable
- So, why would you reuse a parameter type
October 30, 2025 at 8:57 PM
Everybody can reply
Developers: GraphOS Operator for Kubernetes gives you out-of-the-box best practices for GraphQL automation.
No custom orchestration. Developers easily deploy new GraphQL environments. Consistent runtime config across cloud-native architectures.
🔗https://apollographql.pulse.ly/dr24wlxr6c
No custom orchestration. Developers easily deploy new GraphQL environments. Consistent runtime config across cloud-native architectures.
🔗https://apollographql.pulse.ly/dr24wlxr6c
Apollo GraphOS Operator
Kubernetes-native way to deploy and manage GraphQL environments at scale.
apollographql.pulse.ly
October 30, 2025 at 7:00 PM
Everybody can reply
1 likes
GraphQL subscriptions are easy… right?
Turns out, getting them to work in production at scale is a whole other story.
Message queues, WebSockets, SSE, workers, connection limits: it’s all here.
🎥 Watch Laurin Quast from The Guild break it down 👇
youtu.be/eeey6nUQDaE
Turns out, getting them to work in production at scale is a whole other story.
Message queues, WebSockets, SSE, workers, connection limits: it’s all here.
🎥 Watch Laurin Quast from The Guild break it down 👇
youtu.be/eeey6nUQDaE
Why GraphQL Subscriptions in Production Aren’t as Easy as You Think - Laurin Quast, The Guild
GraphQL Subscriptions can super-charge any application but add layers of complexity. Let's delve into the practical aspects of moving GraphQL Subscriptions f...
www.youtube.com
October 30, 2025 at 4:00 PM
Everybody can reply
1 reposts
1 likes
1 saves
Completely in on #SSE (#ServerSentEvents) usage. You can even do this with #graphql. 😄
Leave updates only from SSE. Model all mutations, but one way to ingest updates as they are available. No poll, websockets, or error handling chaos. Just SSE. 😉
Leave updates only from SSE. Model all mutations, but one way to ingest updates as they are available. No poll, websockets, or error handling chaos. Just SSE. 😉
Misunderstanding SSE - YAGNI Club
On my path of practicing simple software my existing understanding of systems, protocols and tools are challenged. My mental model for SSE (Server Sent Events) was a way to keep a connection open and…
yagni.club
October 30, 2025 at 3:50 PM
Everybody can reply
Fragment colocation in Apollo Client 👀 an essential GraphQL concept www.youtube.com/watch?v=a7O8...
Fragment colocation in Apollo Client
YouTube video by Apollo GraphQL
www.youtube.com
October 30, 2025 at 11:11 AM
Everybody can reply
1 reposts
2 likes
If you missed last week's GraphQL meetup or wish to relive it, the replay is now available!
📽️ youtu.be/D8dlHdovZdg
📽️ youtu.be/D8dlHdovZdg
October 30, 2025 at 11:11 AM
Everybody can reply
1 likes
From GraphQL to Zod: Simplifying Arte's API Architecture https://marmelab.com/blog/2025/10/29/from-graphql-to-zod.html
October 30, 2025 at 8:17 AM
Everybody can reply
1 likes
Search boxes will become prompt boxes. Content retrieval will be replaced by content generation.
Apollo #MCP Server makes #GraphQL APIs accessible to AI agents in minutes. GraphOS gives platform teams the infrastructure to support agentic workloads.
https://apollographql.pulse.ly/t7ts2zszg4
Apollo #MCP Server makes #GraphQL APIs accessible to AI agents in minutes. GraphOS gives platform teams the infrastructure to support agentic workloads.
https://apollographql.pulse.ly/t7ts2zszg4
GraphQL Summit 2025 Product Highlights: Building the future of AI and Apps | Apollo GraphQL Blog
Unlock microservices potential with Apollo GraphQL. Seamlessly integrate APIs, manage data, and enhance performance. Explore Apollo's innovative solutions.
apollographql.pulse.ly
October 29, 2025 at 10:00 PM
Everybody can reply
1 reposts
1 likes
How other people keep looking at AI: "How can I use ai to incorporate Liveview + Ash + Hologram + Svelte + Vue + React + Tailwind + Daisy UI + Auto gen OpenAPI/GraphQL + Lua Embeded in Elixir + ect ect ect."
Me: "How do I use AI to remove as many 3rd party deps as possible".
Me: "How do I use AI to remove as many 3rd party deps as possible".
October 29, 2025 at 4:24 PM
Everybody can reply
1 likes
Is your GraphQL API ready for AI agents? Explore strategies like self-describing schemas, machine-friendly errors, and versioning.
How to Prepare GraphQL APIs For AI Agents | Nordic APIs |
Best practices to prepare your GraphQL API for AI agent consumption, from schema introspection to query limits and error handling.
nordicapis.com
October 29, 2025 at 12:18 PM
Everybody can reply
Full Stack GraphQL With Next.js And Vercel
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie…
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie…
Full Stack GraphQL With Next.js And Vercel
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et ac cumsan et iusto odio dignissim qui blandit praesent consectetur adipiscing idealorem.
yuvaearnings.com
October 29, 2025 at 8:03 AM
Everybody can reply
2 likes
Pickbazar- Multivendor Laravel Ecommerce with React, Next Js, GraphQL REST API
https://code.stylelib.org/?p=140919
#codecanyon #ecommerce #laravel #phpscripts #shoppingcarts
https://code.stylelib.org/?p=140919
#codecanyon #ecommerce #laravel #phpscripts #shoppingcarts
October 29, 2025 at 6:15 AM
Everybody can reply
Full Stack GraphQL With Next.js And Vercel
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie…
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie…
Full Stack GraphQL With Next.js And Vercel
Horem ipsum dolor sitter metting Great consectetur adipiscing idealorem ipsum dolor sitter mettingtablished of a page when lookinThe point of using Lorem Ipsu ss normal distribution.est, qui dolor emr ipsum quia dolor sit ame consec tetur. Esse mo lestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et ac cumsan et iusto odio dignissim qui blandit praesent consectetur adipiscing idealorem.
yuvaearnings.com
October 28, 2025 at 9:22 PM
Everybody can reply
2 likes
Specifically because we use lots of fragments and the base operation validation algorithm cost in graphql-js doubles every 10 fragments! See tech.new-work.se/graphql-over...
GraphQL: Overlapping Fields Can Be Merged Fast
Working on a challenging problem is rewarding, especially if you can make progress and share the results; that’s how my past few weeks at…
tech.new-work.se
October 28, 2025 at 8:03 PM
Everybody can reply
2 likes
1 saves
Meet Andrew Thomas-Worsley: Data Engineer & former Frontend Dev with a B.A. in International Business from Pace University.
Skilled in Python, JS, React, SQL, AWS & more, Andrew uses data to drive innovation & impact.
Connect: linkedin.com/in/andrewjworsley
#techtalent #techhire
Skilled in Python, JS, React, SQL, AWS & more, Andrew uses data to drive innovation & impact.
Connect: linkedin.com/in/andrewjworsley
#techtalent #techhire
October 28, 2025 at 8:01 PM
Everybody can reply
entrypoints without server support.
- Currently, it targets GraphQL + React + JS, but all of those are implementation details (e.g. the user never writes GraphQL)
Lots of other advantages! Check out the quickstart, too: isograph.dev/docs/quickst...
- Currently, it targets GraphQL + React + JS, but all of those are implementation details (e.g. the user never writes GraphQL)
Lots of other advantages! Check out the quickstart, too: isograph.dev/docs/quickst...
Quickstart guide | Isograph
In this quickstart guide, we will create a new NextJS project and add Isograph to it. Then we'll use the free and publicly available Star Wars GraphQL API.
isograph.dev
October 28, 2025 at 5:29 PM
Everybody can reply
You're using GraphQL fragments wrong.
They're not for reuse, they're for co-location.
Here's what Meta learned refining this idea 👇🏼
youtube.com/watch?v=gMC...
They're not for reuse, they're for co-location.
Here's what Meta learned refining this idea 👇🏼
youtube.com/watch?v=gMC...
How To Use Fragments (They're Not for Re-use!) - Janette Cheng, Meta
The most natural way to understand fragments is as a reusable part of a query. We at Meta know that this isn't true and can lead to a world of pain when it c...
www.youtube.com
October 28, 2025 at 4:00 PM
Everybody can reply
3 reposts
3 likes
1 saves
Yep, we use a vendored version of the older TS relay compiler via graphql-tools/relay-operation-optimizer as a build step specifically to apply the flatten transform on our top-level fragments
October 28, 2025 at 3:15 PM
Everybody can reply
3 likes
⚙️ Highlights:
• CVE-2025-11702 (CVSSv3 8.5) — Runner API improper access control
• CVE-2025-10497 (7.5) — DoS in event collection
• CVE-2025-11447 (7.5) — DoS in GraphQL JSON validation
#CVE #GitLab #ApplicationSecurity #DevSecOps 🧵3/7
• CVE-2025-11702 (CVSSv3 8.5) — Runner API improper access control
• CVE-2025-10497 (7.5) — DoS in event collection
• CVE-2025-11447 (7.5) — DoS in GraphQL JSON validation
#CVE #GitLab #ApplicationSecurity #DevSecOps 🧵3/7
October 28, 2025 at 2:42 PM
Everybody can reply
You've been holding your #GraphQL fragments wrong all this time.
You’re using GraphQL fragments wrong.
They’re not for reuse, they’re for co-location.
Here’s what Meta learned refining this idea 👇🏼
youtube.com/watch?v=gMCh...
They’re not for reuse, they’re for co-location.
Here’s what Meta learned refining this idea 👇🏼
youtube.com/watch?v=gMCh...
How To Use Fragments (They're Not for Re-use!) - Janette Cheng, Meta
YouTube video by GraphQL Foundation Talks
youtube.com
October 28, 2025 at 2:03 PM
Everybody can reply
1 likes