Multi-tenant WooCommerce Stores Conversion to Headless and Typesense
TLDR 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.
2
Mar 17, 2023 (7 months ago)
Campbell
08:58 AMWe're converting multiple WooCommerce stores to headless, and we'll use typesense for both search/filtering , but also as a better alternative to graphql for retrieving store data such as product, category and general site info.
We expect we'll manage 100+ stores, and each will need data in Typsense. Should we use a single cluster and have all sites write to the same collections, and use Scoped Search Keys for each frontend, or is there a better way to do this? Perhaps each site should have it's own separate collections for category, product, page etc?
Kishore Nallan
11:13 AMThe other thing to keep in mind is that synonyms and curation are stored at a collection level so if you plan to use those features, then you have to use 1 collection per customer.
Campbell
11:43 AMKishore Nallan
11:44 AMCampbell
11:46 AMproduct-125
, product-126
and tie/restrict the api key to the relevant collections.Kishore Nallan
11:47 AMKishore Nallan
11:48 AM2
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Discussing Multi-Tenancy in Typesense Server
Jack enquired about collection organization in typesense server for multi-tenancy solutions. Kishore Nallan suggested creating a collection for each customer.
Integrating TypeSense with WooCommerce
Fabio inquired about any existing or in-progress projects for integrating TypeSense with WooCommerce. Jason made them aware of a community-driven effort and suggested adding their support to it. Fabio revealed they had initiated the project, but lacked assistance. They decided to restart work on the project. Jason suggested modeling the integration after an existing WordPress plugin.
Multiple Filters and JSON Requests in Typesense
Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.