3 ms·
Is graphql support on the roadmap? Why did you go with elixir for subscriptions?
by agustif 6y ago
Is graphql support on the roadmap?
Why did you go with elixir for subscriptions?
- kiwicopple 6y agoAt this stage we don't have plans to support GraphQL. We're a small team so we have to be very strategic which technologies we choose to maintain velocity. Since we use PostgREST, we already support many of the key benefits of GraphQL[1]. That being said, we're big fans of Graphile (https://www.graphile.org/ https://www.graphile.org/). Even if we don't support it ourselves, it would be simple for any dev to point graphile to the Postgres instance and get a "free" graphql API. > Why did you go with elixir for subscriptions? I actually built the realtime server last year to replace Firebase. I needed websockets (it was for a chat app), so elixir (Phoenix) was the right tool for the job. [1] Resource embedding: http://postgrest.org/en/v7.0.0/api.html#resource-embedding http://postgrest.org/en/v7.0.0/api.html#resource-embedding
- agustif 6y agoYeah that makes total sense (focusing on strategic tech). Also hadn't thought about plugging in graphile, I guess that makes sense. I also saw in the repo you don't have TS in mind for now (It could be great later down with a big codebase) I'm small contributor to an accounts javascript package (AccountsJS), it can be used with different dattabases (Mongo, TypeORM, Redis, etc), and transports (Rest, GraphQL) In case you might wanna consider it in the future!
- agustif 6y agoOn the elixir/phoenix choice for WS, I guess that makes sense too, I diped my toes on eelixir a long time ago after starting learning to code with ruby. It was cool, but I found a better home at JS/TS. You can have WS with graphql-subscriptions and postgresql-subscriptions for example too, all in node/js and frontend with apollo / react or vue or angular what you like