Setting Up Typesense in GCP with HA and Ingesting Data
TLDR Rengarajan inquired about setting up Typesense with HA in GCP and using other data sources for ingestion besides mongo or firebase. Joshua and Kishore Nallan provided information and offered to further discuss the matter over a call.
Oct 14, 2021 (27 months ago)
We also see documentation about MongoDB integration with Typesense and Firebase with Typesense. Assuming that these would be available for any document based ingestion with the APIs provided, can we leverage the managed services in GCP?
for mongo, as long as the managed mongo supports change streams that are accessible to your typesense nodes, it should be fine: https://typesense.org/docs/guide/mongodb-full-text-search.html#step-2-start-a-mongodb-replica-set
Kishore Nallan03:15 PM
> If we setup HA by ourselves, would we need to ingest data into two zones if we want to implement HA by ourselves as we are not able to find any replication across zones?
You will just set up a cluster whose nodes that are across regions. You don't have to do anything special from Typesense perspective. There might be additional latency but Typesense will handle it.
> Assuming that these would be available for any document based ingestion with the APIs provided, can we leverage the managed services in GCP?
I don't quite understand this question. Can you please elaborate? Are you using Mongo as the primary data store?
Kishore Nallan03:33 PM
Kishore Nallan03:38 PM
Feel free to pick a time that suites.
Kishore Nallan05:12 PM
I've DMed you
Indexed 3011 threads (79% resolved)
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.
Handling Kinesis Stream Event Batching with Typesense
Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.
Understanding Typesense with Java and MongoDB
Vasudev needed help implementing a Java project with Typesense and MongoDB. Kishore Nallan guided them in designing the project, explaining different methods, providing templates, and responding to error issues. At last, Vasudev successfully implemented the project and expressed gratitude.
Database Management and Personalized Search Queries Discussion
Alexander posed several database and search-related questions. Mac suggested considering GraphQL, considering performance and high availability needs, and leveraging Cloudflare workers. Kishore Nallan provided insights on the capabilities of Typesense and discussed the idea of search personalization using machine learning.
Issue with Typesense Go-Client and Upserting Documents
Anton experiences issues with upserting documents and data getting lost when using Typesense Go-Client. Jason suggests troubleshooting via a call, details of which are not available in the thread.