Svoboda | Graniru | BBC Russia | Golosameriki | Facebook
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis doc #394

Merged
merged 23 commits into from
May 21, 2024
Merged

Redis doc #394

merged 23 commits into from
May 21, 2024

Conversation

kmoscoe
Copy link
Contributor

@kmoscoe kmoscoe commented May 15, 2024

No description provided.

@kmoscoe kmoscoe requested review from dwnoble and keyurva May 15, 2024 17:25
@kmoscoe
Copy link
Contributor Author

kmoscoe commented May 15, 2024

Don't bother reviewing all the merged changes. Just the launch_cloud.md file.

custom_dc/deploy_cloud.md Outdated Show resolved Hide resolved
custom_dc/deploy_cloud.md Outdated Show resolved Hide resolved

We recommend that you use a caching layer to improve the performance of your database. We recommend [Google Cloud Redis Memorystore](https://cloud.google.com/memorystore), a fully managed solution, which will boost the performance of both natural-language searches and regular database lookups in your site. Redis Memorystore runs as a standalone instance in a virtual private cloud (VPC) network, to which your Cloud Run service connects using a [VPC connector](https://cloud.google.com/vpc/docs/serverless-vpc-access).

In the following procedures, we show you how to create a Redis instance in your project's "default" VPC network. You may wish to set up your own new VPC network; if so, follow the documentation in [Create and manage VPC networks](https://cloud.google.com/vpc/docs/create-modify-vpc-networks) substitute that network name for `default` throughout these procedures.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

technically the redis instance doesn't live in the customer's VPC network, it lives in a Google-managed VPC, and connects to the customer's network ("default" or otherwise) via direct peering

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be sufficient to something like say: "we show you how to create a Redis instance that connects to your project's "default" VPC network."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this; I knew I didn't have it quite right. :-) PTAL.

In the following procedures, we show you how to create a Redis instance in your project's "default" VPC network. You may wish to set up your own new VPC network; if so, follow the documentation in [Create and manage VPC networks](https://cloud.google.com/vpc/docs/create-modify-vpc-networks) substitute that network name for `default` throughout these procedures.

### Step 1: Create the Redis instance

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe mention this a sample configuration, and can be tuned as needed

@kmoscoe kmoscoe merged commit 6df687c into datacommonsorg:master May 21, 2024
1 check passed
@kmoscoe kmoscoe deleted the redis_doc branch May 21, 2024 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants