aws-samples / aws-step-functions-long-lived-transactions
Deal with the complexities of dealing with a long lived transaction across distributed components in your microservices architecture using AWS Step Functions.
Summary
  |
|||
| Main Code: 1,164 LOC (11 files) = GO (50%) + YAML (50%) | |||
| Duplication: 34% | |||
| File Size: 0% long (>1000 LOC), 65% short (<= 200 LOC) | |||
| Unit Size: 0% long (>100 LOC), 88% short (<= 10 LOC) | |||
| Conditional Complexity: 0% complex (McCabe index > 50), 100% simple (McCabe index <= 5) | |||
|
|
Logical Component Decomposition: primary (9 components) | ||
|
|
3 years, 4 months old
|
||
|
|
0% of code updated more than 50 times Also see temporal dependencies for files frequently changed in same commits. |
||
| Goals: Keep the system simple and easy to change (4) | |||
|
Features of interest:
TODOs
1 file |
|||
Latest commit date: 2021-07-06
|
0
commits
(30 days)
0
contributors
(30 days) |
|