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

Multiple prod deployments #136

Open
hannahhoward opened this issue Feb 19, 2025 · 0 comments
Open

Multiple prod deployments #136

hannahhoward opened this issue Feb 19, 2025 · 0 comments
Assignees

Comments

@hannahhoward
Copy link
Member

hannahhoward commented Feb 19, 2025

What

After we remove remaining issues in indexer slow down, we may still be hitting latency of just having a single global indexer.

We may want to deploy up to 5 global indexers to give ourselves the best TTFB we can get. Cost to run these is relatively low (few hundred a month), especially if we drop the cache size significantly, which currently looks pretty doable.

Let's hold on doing this till all other optimizations ship, but this may be the next required step.

We'd need to setup Route 53 to intelligently route people to the closest indexer, but this is definitely available as a pretty standard Lambda feature

Alternatively, we can consider putting cloud front in front (as we currently do with content claims), but that will likely be more expensive and less like the ultimate network topology

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Sprint Backlog
Development

No branches or pull requests

2 participants