Optimizing Latency and Cost with a Caching HTTP Reverse Proxy on GCP
Question
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website.
This specific reverse proxy consumes almost no CPU.
You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes.
You want to minimize cost.
How should you run this reverse proxy?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B.
To run a single caching HTTP reverse proxy on GCP, with a 30-GB in-memory cache and an additional 2 GB of memory for other processes, while minimizing cost, we need to choose the best option among the provided answers:
A. Create a Cloud Memorystore for Redis instance with 32-GB capacity: This option would work well as Memorystore for Redis is a fully managed in-memory data store service offered by Google Cloud that provides a highly scalable, low-latency data store. It would be cost-effective as it is a managed service and we only pay for the capacity we use. Also, the Redis instance can be configured to store data entirely in-memory, which provides low-latency access to data. This option meets all the requirements and would be a good choice.
B. Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory: This option is not the most cost-effective as we would need to pay for the Compute Engine instance, which can be costly. Additionally, choosing an instance with more vCPUs than required for a low-CPU usage application can lead to unnecessary costs.
C. Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes: This option is also not the most cost-effective as it involves running Kubernetes Engine, which can be expensive. Additionally, n1-standard-32 instances have high vCPUs, which are not required for this application. Using a larger instance size than required leads to additional costs.
D. Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 G: This option is not the most efficient as it uses an instance type with fewer resources than required, which can lead to performance issues. Additionally, adding a persistent disk can increase the cost.
Therefore, option A (Create a Cloud Memorystore for Redis instance with 32-GB capacity) is the most cost-effective and efficient option for running a single caching HTTP reverse proxy on GCP with a 30-GB in-memory cache and an additional 2 GB of memory for other processes.
