Mercure VS Absinthe Graphql

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)

The Elixir ecosystem loves GraphQL so, if you're interested in going that direction, there's good tooling and plenty of support with absinthe.

We did not expect GraphQL tooling in Elixir to be so good. Absinthe is a comprehensive GraphQL toolkit for Elixir that is incredible to use.

https://github.com/absinthe-graphql/absinthe/issues/387#issuecomment-730726272

Thanks for the other suggestions also, I've never tried lodash but it looks interesting. The REST API stuff should be doable, it's just that I've never done this before. I've built small and simple APIs but never had to integrate them with a frontend. Elixir has a Absinthe to deal with GraphQL, but I don't think I need it right now, so REST is easier.

Actually, dynamic Enum values support was added to absinthe v1.6.0 (https://github.com/absinthe-graphql/absinthe/pull/1023, released 2 months ago) and list support was fixed in v1.6.2 (https://github.com/absinthe-graphql/absinthe/pull/1041, released almost a month ago). It looks like you don't need to add such workarounds since then.