Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to Typesense Cloud #1609

Open
Mephistic opened this issue Aug 31, 2024 · 1 comment
Open

Migrate to Typesense Cloud #1609

Mephistic opened this issue Aug 31, 2024 · 1 comment
Labels
backend Backend Development tech debt

Comments

@Mephistic
Copy link
Collaborator

Problems

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

Additional Links

@Mephistic Mephistic added backend Backend Development tech debt labels Aug 31, 2024
@Mephistic
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend Development tech debt
Projects
None yet
Development

No branches or pull requests

1 participant