-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Spike] rethink our backend infra #904
Comments
Below is a summary of the current chains we support and options for obtaining that data. It is important to highlight that NowNodes is incredibly eager to work with us and would probably be willing to add support for the missing EVMs that have nodes for, but no explorer or WSS support. This would potentially mean we could rely on one provider for everything with the exception of thorchain that we could host ourselves for the time being. NowNodes has additional chains that we have also deprecated in the past due to the inability to justify the expense (osmo for example). Not only would this unlock ~25,000 / a month in cost savings it also means that new chains could be added with a much smaller lift in the future
|
Worth cost evals on 1inch, infura, and (sigh) the graph |
Open Questions:
|
Moving forward with nownodes at this time. Calling this spike done. |
Overview
Unchained is currently very expensive to run and maintain. If we consider labor and AWS costs, we are spending something around 40K / month on it. Its reliability has been spotty at best, between underlying node issues, mysterious timeouts and database corruptions during syncing its worth us collectively evaluating its suitability for our use case. Customers are frustrated with the reliability of our application and we are delaying the launch of features in order to test them against a known working backend. While running our own nodes could be a valuable service, if those nodes aren't stable enough and don't offer enough redundancy for production use, we aren't providing any value and spending significant DAO resources to do it.
The basic needs of our application could potentially be served from a variety of different providers who have much better guarantees around uptime (>99.9%) and are far more cost effective (< 1k / month). There may not exist a single provider that offers all of the chains that we require, and we may still choose to provide an abstraction over their APIs to simplify implementation, but regardless this issue has to be addressed.
References and additional details
Potential providers:
Acceptance Criteria
The output of this spike should be the following
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: