Mercure VS API Platform

Are you aware of things like websockets and mercure.rocks?

It could be implemented with STOMP, or Mercure (goes well with API-Platform, written in PHP/Symfony), you could write your own with the help of nchan and scale it via Redis. If it's a web service, the best practices for operating and scaling are well established, Godot then just becomes another client.

You can try https://mercure.rocks/.

It's worth looking at something like Mercure , which is used by API Platform

Pusher might be one of these systems, Mercure is another one (which you can host yourself). Mercure has good documentation and some examples in various languages, including PHP: https://mercure.rocks/docs/ecosystem/awesome#examples.

You can use Mercure https://mercure.rocks/ , Mercure uses http2.

I actually was thinking about this when I saw https://github.com/dunglas/mercure project to become a Caddy plugin. But I did not find enough reasoning to try this with Centrifugo at that point, and still... Seems awesome from one side - tight integration with a web-server, no extra network between LB and Centrifugo. But will this be useful in practice and find its users? 🤔 That's the question I don't have an answer yet.

Polling is kind of ok (data might change between poll events), but real-time updates are better. So If you don't mind adding an extra service, then take a look at mercure.

Two more questions: - Am I to understand The Guild now recommends GraphQL Yoga over Helix? - Could something like Mercure be included in the recipes ? (this would be a nice solution for serverless)

Technically API Platform is not part of Symfony. Although, they are both French. 😉

Probably API-platform. The website is down at the moment, but: https://github.com/api-platform/api-platform It's Symfony based (and plays nice in that ecosystem), also allows you to describe entities via Schema org vocab, has a client generator, and comes with docker-compose and helm charts. I've used it extensively to build various headless services. It's really easy to expose annotated Doctrine entities.

API Platform is a framework for API-first projects, built on top of Symfony components. Let's see how to create a minimal and lightweight starter project in just 5 minutes!

Just use a nice framework like Symfony and for an API there is a nice thing called API Platform

On the Symfony side, a headless API can be built really quickly with https://api-platform.com/. You describe your domain entities with Schema.org vocabulary, can use a client generator to hammer out a UI in Next, Nuxt, Quasar, or whatever as a starter, it comes with an admin backend, and a Helm chart to deploy on Kubernetes. Works great for APIs when paired with, say Nuxt SSGs/PWAs if you want more of a JAMstack approach.

It could be implemented with STOMP, or Mercure (goes well with API-Platform, written in PHP/Symfony), you could write your own with the help of nchan and scale it via Redis. If it's a web service, the best practices for operating and scaling are well established, Godot then just becomes another client.

Why would someone use this over API Platform?