glimesh.tv VS Absinthe Graphql

Source Code

We use Phoenix and LiveView to power all of our non-video interactions on Glimesh.tv[0] and the immediate out of the box features and performance are unmatched. LiveView allowed us to get a completely real time updating channel where streamers can edit their metadata (game, title, viewer count, etc) and all of the viewers can see it in real time. Not to mention we implemented a distributed chat system that sends message updates in real time to both browser clients and API clients. Both of these features combined amount to less than 1000 lines of code and "just work" across multiple web nodes.

It can be daunting to jump into such a strange world as a LiveView environment may look (Elixir syntax, OTP terminology, etc) but honestly once you dig in deeper, everything just makes sense. LiveView (and HEEx) continue to be very simple to understand abstractions on top of the rock solid OTP platform. It's a joy to build real time applications using it, and I very much appreciate the "developer experience" focus both Chris & Jose have for us Elixir devs!

I'm excited for the launch of Phoenix 1.6 and HEEx is shaping up to be a complete replacement for your traditional SPA + Backend API, and using one consistent language for your full stack really has very freeing & powerful benefits, especially for small teams!

[0] https://github.com/Glimesh/glimesh.tv/

You're also right on the subscription statement in the FAQ, I've submitted a bug for us to fix here: https://github.com/Glimesh/glimesh.tv/issues/687

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.