Friday, October 26, 2018

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

Hi,

I really don't get why you would want to do that? If you are doing only a "standard" website - you don't want or NEED the extra complexity of running DRF. It's not that DRF is hard to setup - but for example if you want to present a list of items - in "standard" django, you create the list and add it to the context data. In DRF - you need to create the list, serialize it into json (or xml if you want to go that route), on the frontend you then need to deserialize the list and present it.

You add a lot of complexity and need to write a lot of frontend code.

Working with "standard" django - you can cache a lot of things in different places. You can for example cache an entire response with template, or just cache the database calls and present them in a template. This is not hard to cache or to setup. 

I think I would need to know more about your use case to understand it better :-)

Regards,

Andréas


Den fre 26 okt. 2018 kl 03:44 skrev Tyler Lynch <tyleralynch@gmail.com>:
I have no need for an externally consumable API, but I am interested in using Django-Rest-Framework simply for performance reasons. 

I'm led to believe that by decoupling my front and back end and then simply consuming the DRF api within views, that I can setup a better caching system? Does this make sense? Using DRF from an architectural standpoint (with the goal of optimizing caching & performance) despite not needing an externally used API? Or am I totally off base and confused? Any advice would be much appreciated.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/8b55ff9a-e915-4546-bf3c-1b20a25e4826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAK4qSCeFqeGT8EbZFbWOGpHKY36D4bwvayLBxGm0YsBBFX6jnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment