| Note |
|---|
|
This decision has been migrated to the Technical Council's Decision Log as part of a consolidation effort. See: DR-000028 - Check Out Performance000029 - Data consistency and message driven approach |
| Page Properties |
|---|
| Status | | Status |
|---|
| colour | Yellow |
|---|
| title | IN PROGRESS |
|---|
|
|
|---|
| Stakeholders | Front-end and back-end devs who meet issues with data consistency |
|---|
| Outcome |
|
|---|
| Created date | |
|---|
| Owner | |
|---|
|
...
- Implementing business transactions that span multiple services is not straightforward,
- Implementing queries that join data that is now in multiple databases is challenging.
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODORDERS-399 |
|---|
|
...
| Status |
|---|
| colour | Blue |
|---|
| title | Priority 1 |
|---|
|
eventual consistency for redundant / duplicated data when some data is duplicated in 2 storages and is to be synchronized,| Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | Priority 2 |
|---|
|
consistency for dangling / lost references when an item is deleted from one module leaving lost references to it in other modules, a problem that is succinctly, if frustratingly, captured in the PR discussion related to UITEN-128.| Status |
|---|
| |
|---|
| colour | Grey |
|---|
| title | Priority 3 |
|---|
|
data consistency during distributed business operations when data in several separate storages is to be modified (mod-finance-storage, mod-invoice-storage, mod-orders-storage),- updates collisions ... (check with Jacub? )
...
- Pair of RefNumber and RefType should be in consistence state between POL and invoice line
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODORDERS-421 |
|---|
|
- mod-orders → mod-invoice
- 1-to-1 relation - one pair of refNumber/refNumberType to one invoice record (
- not sure, need to confirm)
- VendorCode should be in consistence state between Organization record and purchaseOrder.vendorCode
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODORDERS-398 |
|---|
|
- mod-organizations → mod-orders
- 1-to-many relation - one vendor code can be used in many orders
- FundCode should be in consistence state between Fund record and pol.fundDistribution.code
- mod-finance → mod-orders
- 1-to-many relation - one fund code can be used in many orders
...
| Drawio |
|---|
| border | true |
|---|
| |
|---|
| diagramName | Eventual Consistency for redundant data |
|---|
| simpleViewer | false |
|---|
| width | 700 |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| diagramDisplayName | |
|---|
| lbox | true |
|---|
| diagramDisplayName | diagramWidth | 934 |
|---|
| revision | 5 |
|---|
|
Work breakdown draft structure
...
| Drawio |
|---|
| border | true |
|---|
| |
|---|
| diagramName | Eventual Consistency for Redandunt Data, option 2 |
|---|
| simpleViewer | false |
|---|
| width | 1000 |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| diagramDisplayName | |
|---|
| lbox | true |
|---|
| diagramDisplayName | diagramWidth | 1243 |
|---|
| revision | 2 |
|---|
|
...
Deletion of core-module records may leave dangling references from non-core modules
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UICR-125 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIOR-682 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIREQ-589 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIU-2082 |
|---|
|
...
Jira tickets:
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODORDERS-399 |
|---|
|
...
Raman shared current status and suggested plan; Thunderjet is ok to go ahead| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIREC-135 |
|---|
|
- this is a top priority issue with data consistency for duplicated data which is necessary for current Thunderjet feature completion; agree to start with this issue- Raman to work with Andrei Makaranka on details