#community-help

Discussion on Typesense Cloud Infrastructure and Usage

TLDR Juri asked about the infrastructure behind Typesense Cloud and its usage of in-memory cache. Jason revealed it’s hosted on AWS and does not use redis as Typesense is an in-memory data store.

33mo

Join the chat

May 11, 2021 (33 months ago)

Photo of md5-756d5da34cc5127c88730a39db749024

Juri

10:49 PM

BTW What do you use behind the scenes? AWS? GCP? Digital Ocean?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:49 PM

For Typesense Cloud, we're on AWS

May 12, 2021 (33 months ago)

Juri

01:22 AM

Are you using redis for the in-memory cache?

Jason

01:50 AM

No we don't use redis. Typesense is itself an in-memory data store

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Typesense Data Storage Issue with Cloud Run

Rizky inquired about data storage when Typesense is run on Cloud Run. Jason clarified that Typesense needs persistent data storage which Cloud Run doesn't offer.

12mo

Troubleshooting Typesense Document Import Error

Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.

10mo

Discussion on Deploying Typesense on Render.com

Matthias shared their deployment template for Typesense on Render.com which led to a discussion with Jason about docker volumes and memory allocation. Janaka made a point on private deployment.

21mo