Google Cloud Memorystore VS Django REST framework

I imagine that would work. I'd probably default to a redis https://cloud.google.com/memorystore because it feels more boring to me. Source: 5 months ago

I suggest you to use realtime database. It is cheaper than Memorystore (if you use in Google Cloud) and realtime database has a free tier. Source: 10 months ago

Memorystore is Google-hosted Redis/Memcached. You could set up a virtual machine and install Redis/Memcached yourself, but Memorystore eliminates that extra work and provides you with a well-working cache out of the box. Source: about 1 year ago

Memorystore is the managed cache service on GCP. https://cloud.google.com/memorystore. Source: over 1 year ago

Memorystore, the GCP managed service for cache, is not a service by itself, you need to choice the backend behind with Redis or memcached. These two kinds of configurations for Memorystore do not have the same model pricing. Memorystore for memcached is mostly based on Compute Engine model with pricing based on the number of nodes and vCPU + RAM per node. Even if the model pricing is nearly the same, the... - Source: dev.to / almost 2 years ago

Django Rest Framework seems like the most mature and works great with Django. But its strength, if I understand correctly, is for auto-creating all the necessary endpoints for manipulating models, which might be useful for data entry applications. I know that it's super flexible and probably my use case will be covered, but it seems that this it might get complicated. Source: almost 2 years ago

There is one last thing I'm a little confused on with Django Rest Framework and that's the different between permission classes and authentication classes. Source: about 2 years ago

I am using django-rest-framework. It provides an awesome Django admin style browsable self-documenting API. But anyone can visit those pages and use the interface to add data (POST). How can I disable it? Source: over 2 years ago