Well, I wouldn't say the entire world is moving towards JS server side but it's true that there's more and more usage.
My interest in GraphQL stems from the fact that I feel the shortcomings of REST (especially around data querying and its design). Though maybe I can't yet use it for an external API, I think in the future I might be able to consider it for a "private" one.
The design behind GraphQL really fixes many of the shortcomings of REST.
It's very useful in a frontend world where everything is based on the paradigm of components.
In the particular case of Django/Python, if your project doesn't require great scalability, I believe that Python performance processing GraphQL is excellent.
Thanks Darío. I'm communicating between frontend (Vue) and Server (Flask) using a semi-REST internal API and I'm already annoyed by the amount of data I send to components who don't need all of it :-D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, I wouldn't say the entire world is moving towards JS server side but it's true that there's more and more usage.
My interest in GraphQL stems from the fact that I feel the shortcomings of REST (especially around data querying and its design). Though maybe I can't yet use it for an external API, I think in the future I might be able to consider it for a "private" one.
That's why I asked about Python and GraphQL :-)
The design behind GraphQL really fixes many of the shortcomings of REST.
It's very useful in a frontend world where everything is based on the paradigm of components.
In the particular case of Django/Python, if your project doesn't require great scalability, I believe that Python performance processing GraphQL is excellent.
Thanks Darío. I'm communicating between frontend (Vue) and Server (Flask) using a semi-REST internal API and I'm already annoyed by the amount of data I send to components who don't need all of it :-D