Subdomain registrar improvement #282
Description
Background
Increasing the performance of the subdomain registrar to improve user onboarding on Sigle and on other apps which use the subdomain registrar https://github.com/stacks-network/subdomain-registrar.
The performance of the subdomain is currently an issue, with the API taking more than 2mins to send a response some days. The stability is also a concern, from our tests, 1 out of 5 request is failing.
Project Overview
What solution are you providing? Who will it serve?
Cleanup and increase performance for the subdomain registrar so new projects can onboard users much faster.
Scope
What are the components or technical specs of the project? What will the final deliverable look like? How will you measure success?
Final deliverable will be commited to the main repo.
- Improved performance of registration and stability
- Code migrated to TypeScript
- Database implementation migrated to Postgres
Budget and Milestones
What grant amount are you seeking? How long will the project take in hours? If more than 20, please break down the project into milestones, with a clear output (e.g., low-fi mockup, MVP with two features) and include the estimated work hours for each milestone.
Total Grant Request: $5k
M1: Migrate types from Flow to TypeScript and improve tooling in the repo (prettier, eslint) (3 days)
M2: Migrate usage from the blockstack SDK to the new stacks.js (3 days)
M3: Database migration from sqlLite to Postgres (5 days)
Each milestone can be done as separate pull request to the Stacks repo and would require review / approval from the Hiro team before the next milestone start.
Team
Who is building this? What relevant experience do you bring to this project? Are there skills sets you are missing that you are seeking from the community? Please share links to previous work.
Will be executed by Sigle dev team that has experience both working with the technologies which will be implemented and also Stacks repositories.
Risks
What dependencies or obstacles do you anticipate? What contingency plans do you have in place?
Main risks will be communication and time for review coming from the Hiro team. This could move a lot the deadline of this task.
Community and Supporting Materials
Do you have previous projects, code commits, or experiences that are relevant to this application? What community feedback or input have you received? How do you plan to share your plan to the community over time and as the final deliverable?
You can see some examples of projects we did here Sigle.
Before starting any work on this task we need to validate the plan with Hiro engineers and agree with the implementation approach for postgres.