Skip to content

[epic]: payment db: SQL implementation & migration #9861

@ziggie1984

Description

@ziggie1984

This is the tracking issue for the payments db SQL-ization project. It will be the go-to reference to see how the project is progressing.

I'll start with a check-list for easy reference & then will add any details & context lower down behind some drop-down tags.

  • Create POC with working native SQL implementation => POC Payment SQL Support #9822

  • Make sure all tests pass for both backends

  • Present to reviewers via a presentation document (design doc can be found the the file payment_sql_schema_lnd (second commit) in POC Payment SQL Support #9822

  • Prepare a commit history how the reviewers will have a very easy time to review the change

  • Create Refactor PRs before the main SQL code is introduced + Merging these PRS

  • Introduce SQL schema, queries & CRUD + Merging these PRs

  • Finalize the Migration Code + Merge these PRs

  • Plug the new migration into the main code base & stress test to compare both the databases.

  • Once there is enough confidence in the code & migration, add the SQL impl & migrations to the main prod build

  • Potential refactor: Separate payment lifecycle from HTLC Switch

Sub-issues

Metadata

Metadata

Assignees

Labels

code healthRelated to code commenting, refactoring, and other non-behaviour improvementsepicIssues created to track large feature developmentpaymentsRelated to invoices/paymentssql

Projects

Status

In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions