Recommendations for Running Typesense on GCP
TLDR Alexandru asks about best practices for running Typesense on Google Cloud Platform (GCP). Kishore Nallan recommends using the Compute Engine and setting up a cluster if the data isn't fairly static.
Nov 11, 2021 (22 months ago)
Alexandru
01:12 AMKishore Nallan
02:06 AMOtherwise, yes, clustering is the best approach to have HA. Even though Typesense is in-memory, it can survive restarts because the raw data is kept on disk and is re-indexed on restart.
Alexandru
03:08 AMWhat service would be best suited in GCP? Some of the data might fall under PII over time and we’d love to self-host it.
Kishore Nallan
05:16 AMAlexandru
01:47 PMKishore Nallan
01:48 PMAlexandru
01:53 PMTypesense
Indexed 2764 threads (79% resolved)
Similar Threads
Deploying Typesense on Google Cloud Platform (GCP)
Stephane asked for advice on deploying Typesense on GCP and encountered an issue with persistent storage. Jason suggested using Linux VMs on GCP instead, which Stephane thanked them for and found a solution in the documentation.

Typesense Performance in Cloud Run
Bill asked about the performance of Typesense in Cloud Run. CaptainCodeman and Kishore Nallan expressed doubts about this setup, while Thomas proposed using flexsearch and AWS Lambdas as a suitable alternative.

Discussing Multi-tenant Indexing and Typesense Clusters
Semyon enquired about search and indexing performance for multi-tenant indexing. Virginio suggested using Typesense cloud, but Semyon noted the cost difference against bare metal instances. Jason proposed vertical scaling before multi-cluster setup.


Deploying Typesense on Google Cloud Run
Nicolas attempted to deploy Typesense on Google Cloud Run but encountered problems. CaptainCodeman advised that Cloud Run is unsuitable for Typesense and suggested using a container optimized VM.

Configuring Typesense HA Cluster on AWS
Agustin was looking for best practices to run a Typesense HA cluster on AWS, particularly regarding horizontal scaling. Kishore Nallan recommended using standalone instances or an ASG for static data, rather than clustering.