whitenoise VS django-rest-framework

You can use whitenoise. https://github.com/evansd/whitenoise

We’ll use this library to serve our static admin files. I’m not going to go over all the configuration details here, but you can feel free follow them on your own. Make sure the static files are part of the Lambda package.

I'm trying to serve static files through WhiteNoise as per Heroku's recommendation. When I run collectstatic in my development environment, this happens:

Waitress - for serving your application easily (pairs very well with Whitenoise).

3) Caching static assets - both of static assets. So maybe try deploying a Django app in a production environment and cache the static assets. You could put them behind a service like Cloudflare which will take care of that for you, or have a look at something like [Whitenoise](https://github.com/evansd/whitenoise) which will add the correct HTTP headers for you. You can spend some time reading about HTTP Caching headers and even try writing a simple middleware which caches certain requests to your Django app (just for learning purposes).

FWIW, I always use Whitenoise to serve Static files when I use Heroku, and only keep Media files on AWS. It works well.

In the beginning of the project, I chose Google Cloud Platform as the "Cloud Provider". But for simplicity and easy to use I switched to WhiteNoise to serve staticfiles.

- Django Rest Framework has no async support? https://github.com/encode/django-rest-framework/issues/7260

A URL shortener is a service that transforms long and complex URLs into short, easily memorable ones. This tutorial guides you through creating a URL shortener using Django REST framework and Postgres, deploying it on Koyeb.

Now, I'm converting this app into a Vue-based SPA (still powered by Django). I'm using the Django REST Framework to build the API that the SPA will interact with. (I'll be using token-based auth, via django-rest-knox. ETA: I'll actually be using djangorestframework-simplejwt.)

For the backend, we chose Python, Django Rest Framework. On the frontend, React, Redux, Saga, Sass. Let’s start with the backend, which was managed by Yegor. He writes about the server part of the project himself.

With regard to JSON API aspects of Django, have you used https://www.django-rest-framework.org/ ? I find it to be very satisfactory.

django-rest-framework and the Fetch API, or

Django REST Framework (DRF) Django REST Framework is a famous, powerful, and flexible toolkit for building Web APIs in Django. It provides a set of reusable components and tools to simplify API development, including serialization, authentication, permissions, and view sets.

I wish Django would take async more seriously. This comment gives a pretty good overview of the current situation (some points are more valid than others): https://github.com/encode/django-rest-framework/discussions/...

The Python ecosystem is strange. Where other dev communities will embrace new ways of doing things faster than most people can keep up — the Python community needs to be pulled kicking and screaming into the light once ever decade or so. Python 2 to 3, ~10 years.

async/await has been in Python since 2015, it feels like it's going to be another 5 years before we see people taking async seriously in the big packages. Same problem we had during the 2/3 transition. No library support, no developer support.

Thanks for helping Steve to complete his REST API, he is now partying🥳. You can get more information on how to use the Django REST framework to best way read the documentation. There are many alternatives to the Django REST framework, you can give them a try if you want,

[Django Rest Framework](https://www.django-rest-framework.org/) has the very nice idea of a [ViewSet](https://www.django-rest-framework.org/api-guide/viewsets/#modelviewset) that allows really minimal code to perform all the basic CRUD actions on a model.