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

Epic: Modularization: Updated Roadmap #4710

Closed
84 of 88 tasks
nickpoorman opened this issue Jan 23, 2023 · 0 comments
Closed
84 of 88 tasks

Epic: Modularization: Updated Roadmap #4710

nickpoorman opened this issue Jan 23, 2023 · 0 comments
Labels
Modularization Issues or PRs related to modularization

Comments

@nickpoorman
Copy link
Contributor

nickpoorman commented Jan 23, 2023

Updated Roadmap


Triage


June 9th - Final Date before beginning E2E Testing

Remaining Sprint Backlog Items Ready to Be Pulled


E2E Testing


Iterate++


Final Testing


Future


Old Items

At this point, we can take the workflows into production. We won’t have new code for the handlers, and we won’t be using any of the states or other APIs, but we will have the workflows done and in production. At this point we are using the new gRPC handlers and not the ones in mono-repo.

At this point, all pre-handle work will be in the new code and not in the mono-repo. We can actually ship when ready for individual pre-handles, we don’t have to have them all done to ship any. We can ship them as they are available.

At this point, we will have all queries and all pre-handle running on the production network. In theory, these could be done in parallel with the pre-handle work, we don’t have to finish all pre-handle to get started on queries, but practically it might make sense to have everybody focus on one type of transaction at a time.

At this point all transaction handling code, pre-handle, query, gRPC is all being handled by new business logic, but still on the current merkle tree data structure.

At this point, we can use the Schema APIs for handling schema migrations. Up to this point, we have to use the mono-service migration APIs for handling migrations.

Future

Tests and CI

Merge Platform and Services code together

Metrics and Monitoring


Core Facilities:

  • Properties
  • States
  • Fees
  • Throttles
  • Records
  • Signature Verification

Final state
final state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Modularization Issues or PRs related to modularization
Projects
Archived in project
Development

No branches or pull requests

3 participants