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.

Sign up for GitHub

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

Jump to bottom

perf: indexer risk assessment #182

Open
0xneves opened this issue Feb 12, 2025 · 1 comment
Open

perf: indexer risk assessment #182

0xneves opened this issue Feb 12, 2025 · 1 comment
Assignees
@mschead @0xneves
Labels
status: needs information Waiting for information type: discussion Needs discussion between parties

Comments

@0xneves
Copy link
Contributor

0xneves commented Feb 12, 2025

What could fail in the indexer?
How do we make sure we have a "Plan B" for when it does?
Should we have a second instance for the database?
Should we have a second instance for the streaming process?
Should we have a second node?
@0xneves 0xneves converted this from a draft issue Feb 12, 2025
@0xneves
Copy link
Contributor Author

0xneves commented Feb 12, 2025

Uptime 99.9%:

  • AWS has fragmented data collection, but we need Gateways that remain open to manage user access. And a second emergency gateway.
  • Make sure the application is always running.

Code Error (Health Check):

  • Notify admins when the gateway doesn't respond (make at least 1 API call per minute)

Run into Production (Q&A)

  • Unitary tests (test every single function and routing)
  • API Calls (make sure at least every single API call responds successfully)

@0xneves 0xneves changed the title [INTERNAL PROCESS OPT] INDEXER RISK ASSESSMENT perf: indexer risk assessment Feb 13, 2025
@0xneves 0xneves added type: enhancement Improvements to the codebase status: needs information Waiting for information type: discussion Needs discussion between parties and removed type: enhancement Improvements to the codebase labels Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mschead mschead

@0xneves 0xneves

Labels
status: needs information Waiting for information type: discussion Needs discussion between parties
Projects
Kadindexer
Status: Backlog 📋
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mschead @0xneves