Whatever your want, that is your creation. ^.^
Whatever your want, that is also your creation. ^.^
Also whatever your want, that is your creation. ^.^
Ditto, sensing a pattern yet?
Not really, same decisions with rest. Names of endpoints, connections, what data can be served, how to query for it, etc… etc… etc…
That template is an example, it is not a full REST endpoint, it is for interacting with only a single schema, and I near never see just single schema’s asked for or queried for.
Phoenix has default templates for those too, but again it all depends on just ‘what’ you are trying to accomplish.
GraphQL is just a query, think SQL, but for JSON, still very succinct and simple, it is not bound to any specific transport medium, only that GraphQL is a request and it returns JSON. You can use it over endpoints, channels, raw TCP, whatever. And GraphQL is quite used, there is plenty of documentation on it out there. Using it with channels all I did was just have a single message that I named “request” and I just take the string from it and call absinthe with it and return the results, it is the same thing you do if it is on an endpoint (though it has a plug that can save you that step, though piddly a step it is).
GraphQL Subscriptions are a new GraphQL thing (not in absinthe, they are new in general), it just lets you basically ‘register’ to a query and you get the response like normal, except you keep getting responses again and again as it changes. ^.^
That would be trivial to push over websockets as well.