Syncing Primary Data Store and Typesense
TLDR bnfd asked how to sync primary data store and typesense. robert suggested syncing via API level and considering ORM middleware. Kishore Nallan proposed an ORM hook or use of a queue and daemon, and mentioned the option of running a cron for less frequent updates.
Aug 18, 2022 (16 months ago)
/api/modeli then sync the index for model too.
Aug 19, 2022 (16 months ago)
Kishore Nallan01:42 AM
One way to overcome that is to write to a queue and then have a daemon that reads from queue and indexes into Typesense.
If the updates are not frequent, you could essentially run a cron every 10 seconds to query for updates from the database and index into Typesense as well.
Indexed 3011 threads (79% resolved)
Managing Typesense Across Large Datasets
Phillip inquired about best practices with Typesense for large datasets. Ross shared personal practices, and Jason confirmed Typesense isn't designed to be a primary datastore. Patrick shared a related discussion link. Viji mentioned using DynamoDB Streams as an option.
Efficient Dataset Creation and Maintenance in Typesense with React
sonu asked about Typesense dataset management in a React project. Nick shared their solution using a postgres database, cron, and the import endpoint. Kishore Nallan suggested updating Typesense whenever MySQL data changes and explained primary databases' role. The dataset file would reside with Typesense, not affecting the front-end load time.
Discussing Data Changes and Typesense Update Methods
sonu asked about the efficient way to manage database updates in Typesense. Kishore Nallan suggested a cron-based approach or to queue updates, along with idea of 'is_deleted' flag to handle deletion.