Discussing Multi-Tenancy in Typesense Server
TLDR Jack enquired about collection organization in typesense server for multi-tenancy solutions. Kishore Nallan suggested creating a collection for each customer.
Jul 19, 2023 (2 months ago)
If we have a multi-tenant solution in a single typesense server, would it be better to create a separate collection for each organization, or one table that is scoped with organization field?
About 70% of field names will be the same, but 30% of fields will be custom. Say each customer will have 1000 ~ 20000 items, and there could be over 100 customers.
Is there a preferred way of handling multi-tenancy in typesense?
Kishore Nallan11:37 AM
Jul 20, 2023 (2 months ago)
Indexed 2779 threads (79% resolved)
Managing Data Access with Typesense in SaaS Applications
Alex inquired about data separation using typesense in a multi-tenancy application. Jason suggested using scoped API keys.
Multi-tenant WooCommerce Stores Conversion to Headless and Typesense
Campbell asks for advice on handling multiple WooCommerce stores in Typesense. Kishore Nallan suggests using one collection per customer for flexibility in features like synonyms and curation.
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.