GraphQL strikes me as very similar to NoSQL. Useful in niches but the older standard is better in general.
I've tried both and the added complexity (designing a system to generate all required data from a single request) of GraphQL for the, seemingly minor, gain (a single request for all your data) doesn't enthuse me. It's an interesting solution to a problem I've never really had. Not to say it isn't useful in some situations, I just haven't yet encountered a situation where it is. - Nick On Tue, Nov 12, 2019 at 9:14 AM guettli <guettl...@gmail.com> wrote: > Hi, > > I am new to GraphQL, but I like the idea very much. > > There is already an A Django integration for Graphene: > https://github.com/graphql-python/graphene-django > > > What are the pros and cons of djangorestframework and GraphQL? > > Which one would you choose, if you could start from scratch? > > Regards, > Thomas Güttler > > PS: I am always looking for feedback for my guidelines: > https://github.com/guettli/programming-guidelines > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/f5dd3fea-28ab-4b01-9e07-0819b4bb91cb%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/f5dd3fea-28ab-4b01-9e07-0819b4bb91cb%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAGuvt90HG0OE9kV9axHvkFx8xfa7qD41HdV3tuoupSKYjdG9ew%40mail.gmail.com.
