Discussion on Deploying Typesense on Render.com
TLDR 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.
Aug 27, 2021 (25 months ago)
Asking because Typesense is a stateful datastore and requires both of these to operate
(At the risk of cannibalizing our own cloud hosted version 😅)
I don't think this jeopardises your hosted version as this is far from handling any serious prod load, not to mention providing any high availability.
Mar 26, 2022 (18 months ago)
Indexed 2764 threads (79% resolved)
Discussing Typesense Cloud's SSDs, NVMe, and Resources Needed
A asked about Typesense's storage type and configuration possibilities. Jason shared that they use SSDs and suggested NVMe SSDs for high-availability instances. They discussed server resources needed for specific user cases and briefly touched on DDoS protection via Cloudflare.
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.
Implementing Self-Hosted Typesense in Production
Jainal enquired about implementing Typesense in production with specific questions about open-source disclosure and memory capacity. Jason clarified GPL-3's source code disclosure and explained risks of running out of RAM. Kishore Nallan provided strategies for data durability and clustering.
Discussing RAM, CPU, and Hosting Options for Project
Bill asked about plans, domains and performance disparity with Typesense versus Digital Ocean. Kishore Nallan and Jason provided insights about network and disk performances, comparisons and prices.
Issues deploying Typesense to AWS EKS
Pavan had issues when deploying Typesense to AWS EKS. Kishore Nallan suggested deployment to plain EC2 instances and provided the API key information. Eventually, Pavan resolved the issue with Helm.