You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've dealt with a number of issues due to the complexities of our Typesense setup, namely:
Bugs in updating collection definitions
Lack of expertise in Typesense
Most unique/complicated part of our stack
Highest ongoing cost
In order to simplify our Typesense setup and reduce the operation cost of the search server, we should migrate from our custom Typesense setup to Typesense Cloud.
Success Criteria
Create Typesense Cloud account
Set up a search server with specs (1 GB RAM; 2 vCPUs, 4 hr burst per day; NO high availability; NO search delivery network; region of North Virginia)
This roughly mirrors the current configuration of our privately run Typesense server
Typesense Cloud's pricing estimate is that this will cost ~$30/month for a cluster - given that we run a DEV and PROD server, this is still a significant cost saving with a clear upgrade/scaling path should we get the funding for it.
Reconfigure the Typesense Client to point to the new cloud cluster
The new configuration should be behind a toggleable flag for the initial rollout
Re-index the existing search collections into Typesense Cloud
Should just be able to run the existing indexer job with the new client configuration
Spin down the older cluster
Update Typesense documentation on the MAPLE Github wiki
We should aim to only commit to this work when we have the time and manpower to push it through to completion - running the old and new typesense clusters in parallel will obviously be more expensive than our current setup, so we should aim to spend as little time as possible in that state.
Problems
We've dealt with a number of issues due to the complexities of our Typesense setup, namely:
In order to simplify our Typesense setup and reduce the operation cost of the search server, we should migrate from our custom Typesense setup to Typesense Cloud.
Success Criteria
Additional Links
This may end up being enough work to split into multiple tickets - this is a bit of a brain dump.
The text was updated successfully, but these errors were encountered: