High performance scalable web applications often use a distributed in-memory data cache in front of or in place of robust persistent storage for some tasks. We recommend using Memorystore for Redis as your caching service. Note that Memorystore for Redis does not provide a free tier. See Memorystore Pricing for details.
Before getting started, make sure your app will stay within the Memorystore for Redis quotas.
When to use a memory cache
Session data, user preferences, and other data returned by queries for web pages are good candidates for caching. In general, if a frequently run query returns a set of results that do not need to appear in your app immediately, you can cache the results. Subsequent requests can check the cache and only query the database if the results are absent or have expired.
If you store a value only in Memorystore without backing it up in persistent storage, be sure that your application behaves acceptably if the value expires and is removed from the cache. For example, if the sudden absence of a user's session data would cause the session to malfunction, that data should probably be stored in the database in addition to Memorystore.
Understanding Memorystore permissions
Every interaction with a Google Cloud service needs to be authorized. For example, to interact with a Redis database hosted by Memorystore, your app needs to supply the credentials of an account that is authorized to access Memorystore.
By default your app supplies the credentials of the App Engine default service account, which is authorized to access databases in the same project as your app.
If any of the following conditions are true, you need to use an alternative authentication technique that explicitly provides credentials:
Your app and the Memorystore database are in different Google Cloud projects.
You have changed the roles assigned to the default App Engine service account.
For information about alternative authentication techniques, see Setting up Authentication for Server to Server Production Applications.
Overview of using Memorystore
To use Memorystore in your app:
Set up Memorystore for Redis, which requires you to create a Redis instance on Memorystore and create a Serverless VPC Access that your app uses to communicate with the Redis instance.
Install a client library for Redis and use Redis commands to cache data.
Setting up Memorystore for Redis
To set up Memorystore for Redis:
Create a Redis instance in Memorystore.
When prompted to select a region for your Redis instance, select the same region in which your App Engine app is located.
Note the IP address and port number of the Redis instance you create. You will use this information when you create a Redis client in your code.
Connect your App Engine to a VPC network. Your app can only communicate with Memorystore through a VPC connector.
Be sure to add the VPC connection information to your
app.yamlfile as described in Configuring your app use the connector.
Installing dependenciesTo make the redis-py client library available to your app when it runs in App Engine, add the following line to your app's
The App Engine Python 3 runtime will automatically upload all libraries
requirements.txt file when you
deploy the app.
For local development, we recommend that you install dependencies in a virtual environment such as venv.
Creating a Redis client
To interact with a Redis database, your code needs to create a Redis client to manage the connection to your Redis database. The following sections describe creating a Redis client using the redis-py client library.
Specifying environment variables
The redis-py client library uses two environment variables to assemble the URL for your Redis database:
- A variable to identify the IP address of the Redis database you created in Memorystore.
- A variable to identify the port number of the Redis database you created in Memorystore.
We recommend you define these variables in your app's
app.yaml file instead of
defining them directly in your code. This makes it easier to run your app in
different environments, such as a local environment and App Engine.
env_variables: REDISHOST: '10.112.12.112' REDISPORT: '6379'
Importing redis-py and creating the clientAfter you define the
REDISPORTenvironment variables, use the following lines to import the redis-py library and create a client:
import redis redis_host = os.environ.get('REDISHOST', 'localhost') redis_port = int(os.environ.get('REDISPORT', 6379)) redis_client = redis.Redis(host=redis_host, port=redis_port)
If you've used an older version of redis-py for other apps, you might have used
StrictClient class instead of
Client. However, redis-py now
Client instead of
Using Redis commands to store and retrieve data in the cache
While the Memorystore Redis database supports most Redis commands, you only need to use a few commands to store and retrieve data from the cache. The following table suggests Redis commands you can use to cache data. To see how to call these commands from your app, view your client library's documentation.
|Create an entry in the data cache and
set an expiration time for the entry
|Retrieve data from the cache||GET
|Replace existing cache values||SET
|Increment or decrement numeric cache values||INCR
|Delete entries from the cache||DEL
|Support concurrent interactions with the cache||See details about Redis transactions. Note that the redis-py client library requires all transactions to occur in a pipeline.|
Testing your updates
When you test your app locally, consider running a local instance of Redis to avoid interacting with production data (Memorystore doesn't provide an emulator). To install and run Redis locally, follow the directions in the Redis documentation. Note that it currently isn't possible to run Redis locally on Windows.For more information about testing Python 3 apps, see Testing and deploying your application.
Deploying your app
Once your app is running in the local development server without errors:
If the app runs without errors, use traffic splitting to slowly ramp up traffic for your updated app. Monitor the app closely for any database issues before routing more traffic to the updated app.