Implementing Self-Hosted Typesense in Production
TLDR 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.
Mar 26, 2021 (32 months ago)
Jainal
06:36 PM1. I have seen typesense using GNU General Public License v3.0 license and in it source code must be disclosed if distributed. But since i am not distributing the software and i am basically indexing user info and when user search a particular term on my webapp the results are fetched from typesense. So, in this condition do i need to disclose source if i am using typesense.
2. I have read the docs in which it is written typesense stores results in ram. But, what happens when there no more space remaining in the ram, than does typesense stores them on disk or fails?
Jason
06:39 PMJason
06:40 PMJason
06:42 PMJason
06:43 PMMar 27, 2021 (32 months ago)
Jainal
01:48 PMJainal
01:49 PMif i am deploying typesense on a single vm on cloud. Will it be beneficial to set up a cluster configuration inside a single VM?
Jainal
09:39 PMJainal
10:44 PMJason
11:20 PMMar 29, 2021 (32 months ago)
Jainal
10:17 AMKishore Nallan
10:18 AMKishore Nallan
10:19 AMJainal
10:20 AMKishore Nallan
10:23 AMKishore Nallan
10:24 AMJainal
10:25 AMJainal
10:25 AMKishore Nallan
10:25 AMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Addressing Typesense Server Issues and Optimization Needs
Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.
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.
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.
Setting Up High Availability Cluster in AWS
Retheesh needed help setting up a high availability cluster in AWS. Jason recommended using EC2 instances and provided instructions for setting up typesense nodes.
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.