Memcached

Memcached for TMS: attracs-services-195009-attracs-backend-3 (project: attracs-services-195009) Memcached for other services: adi-devops-confidential-instance-stable-2 (project: attracs-devops)

Memcached configuration and deployment: Old files: attracs-linux-playbooks/services/memcached New files: devops-ansible-server-software/memcached

What has been done

I set up a high-performance, in -memory cached for the drivers portal application to reduce database load and speed up application response time. * Enabled the Cloud Memorystore for Memcached API in the GCP project to authorized the service. * I configured the instance. * The initial size of the instance is 1 node, 1 vCPU, and 1 GB of memory. * Configured Network * I selected the application's main VPC network (default) to ensure the cache is on the same private network as the Go backend. * Completed the one-time setup for Private Services Access This was done by allocating an automatic IP range fir service connection. * Finished the setup and successfully triggered the creation of the Memcached instance. So, to summarize, a fully managed Memcached instance is now running and available in the project, also, unique Discovery Endpoint has been generated.

Pending: Testing, the application has not been connected to it yet. Cost report. How much will actually cost according to the use given to this service. Application deployment and infrastructure provisioning.