#GraphQL for #Drupal 5.0.0-alpha2 released - some minor PHP type updates since alpha1. Please test!

https://www.drupal.org/project/graphql/releases/5.0.0-alpha2

#HTMX is growing on me.

It felt weird at first to generate frontend from the backend. But I gave in because writing more code at the backend was way too tempting. I just can't hold #javascript right.

Using templates and SQL, creating frontend using #php and htmx is pretty nice. Kind of feel like doing #graphql and #Rest together.

But at the end of the day, I am writing less javascript and it is great.

Quarkus GraphQL Quickstart + MinIO as Object Store S3. It's much more than just a Quickstart ;-)
https://github.com/amusarra/quarkus-graphql-quickstart
#GraphQL #Java #quarkus #S3

#ApolloGraphQL launched its #MCPserver, enabling businesses to securely & efficiently integrate AI agents with existing APIs using GraphQL.

Learn more from Matt DeBergalis, CTO and co-founder of Apollo GraphQL, in this interview with #InfoQ https://bit.ly/3Hvsn7y

Supercharge Your Java APIs with GraphQL and Quarkus https://myfear.substack.com/p/graphql-quarkus-java-api-guide
#Java #Quarkus #GraphQL #Microservices

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

Moin #Jax,

hier findet ihr noch die Slides von meinem #GraphQL-Vortrag: https://graphql.schule/jax2025

Vielen Dank, dass ihr dabei gewesen seid. Vielleicht bis zum nächsten Mal

It's crazy that `graphql-depth-limit` (with its Git repository removed and not being updated for 8 years) has 750k weekly downloads, while the actual `@graphile/depth-limit` library (updated, typed, from a GraphQL maintainer) has only 400 downloads.

I've been immersed in GraphQL recently. You know, it's pretty great, actually. Are there issues? Yeah. It's impossible to design a system like this perfectly. Yeah, maybe it was made by "Facebook", but in reality it was made by engineers who worked at Facebook and is controlled by a neutral non-profit. It's does a few things *extremely* better than REST: change/versioning, pulling multiple related or unrelated bits of data in a single request, and only sending the fields you need.

1/n

Good progress on the #dweb REST APIs and improvements to the #OpenAPI docs today, all with the help of #actix and #utoipa

BTW #SwaggerUI is really cool

A few days ago I knew nothing about these but now I have a working API that is documented and can be tested live while reading those docs.

Someone asked if I might support #GraphQL but I haven't looked into that. Convince me that I should!

Directus – real-time REST and GraphQL API of any SQL database

Link: https://github.com/directus/directus
Discussion: https://news.ycombinator.com/item?id=43150116

#SpannerGraph is now generally available (GA)!

Explore new capabilities like the Graph Notebook, GraphRAG with LangChain integration, Graph schema in Spanner Studio, and enhanced Graph query features supporting path data type and functions.

Curious to learn more? Dive into the details here: https://bit.ly/4k3ejBd

#GraphQL federation: what tools are there to handle the #supergraph schema composition? Is it unwise to try to pin some custom logic inside the query planning stage? If I need to do custom authorization remapping, where would that sit?

It looks to me as if #Apollo federation gateway is a subscription-only service that requires an outside online connection... Surely that can't be right? What am I missing?

Edit: found #WunderGraph and #HiveGateway as two other options. And we're being pushed towards #Azure APIM resolver as a temporary solution. This one feels iffy.

GraphQL JIT promet des performances accrues et une économie de CPU. Et sur le papier, comme dans les tests, ça tient la route. Mais après quelques années en production, la réalité est plus nuancée, et les promesses s’estompent. Je vous raconte tout sur mon blog ! https://blog.ztec.fr/2025/post/graphql-jit-est-t-il-vraiment-plus-performant/ #nodejs #graphql #performance

It's often easier to use lab tests to make technical decisions for your system. Yet, behaviors can differ in production, and you may want to revisit your choices in the light of real case scenarios. At Deezer we experimented it with GraphQL JIT and here is my notes : https://deezer.io/graphql-jit-is-it-worth-it-64e66f21dbb8 #nodejs #graphql #performance

«GraphQL-Grundlagen-Tutorial:
GraphQL ist für viele Devs die erste Wahl, um effiziente, zukunftsfähige APIs zu entwickeln. So gelingen die ersten Schritte mit dem Open-Source-Tool.»

Nutzt dies wer im allgemeinen für Web-Produkte, sprich entwickelt damit Web-Apps die allgemein und nicht nur speziefisch nutzbar sind oder bestehen weiter viele auf REST API's? Ich entwickelte damit noch nie was.

https://www.computerwoche.de/article/2835212/graphql-grundlagen-tutorial.html

[News] Agoda’s Unconventional Client-First Transition from a GraphQL Monolith to Microservices by Eran Stiller

https://bit.ly/3ZoB7Tv

Agoda described its approach to transitioning from a monolithic GraphQL API to a microservices architecture. Agoda adopted a client-first strategy, preparing its client apps to handle the monolith and the microservices in parallel using an in-house smart orchestrator library.

[News] Microsoft Announces General Availability of Fabric API for GraphQL by Robert Krzaczyński

https://bit.ly/49aVjvG

Microsoft has launched Fabric API for GraphQL, moving the data access layer from public preview to general availability. This release introduces several enhancements, including support for Azure SQL and Fabric SQL databases, saved credential authentication, detailed monitoring tools, and integration with CI/CD workflows.

Virtuoso Open Source (VOS) 7.2.14 is out!

Our high-performance, multi-model #VirtuosoRDBMS supports:

• Relational tables & graphs
• #SQL, #SPARQL & #GraphQL
• Seamless AI integration w/ #LangChain & #LlamaIndex via #HTTP, #ODBC, or #JDBC

Read on for links etc..