Add DynamoDBHistoryAutoIncrement class for version control in DynamoDB

[dakota002]

This replaces #16 and #17

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (230a672) 92.59% compared to head (2acc2e2) 100.00%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main       #20      +/-   ##
===========================================
+ Coverage   92.59%   100.00%   +7.40%     
===========================================
  Files           1         1              
  Lines          27        39      +12     
  Branches        3         5       +2     
===========================================
+ Hits           25        39      +14     
+ Misses          1         0       -1     
+ Partials        1         0       -1     

Files	Coverage Δ
src/index.ts	100.00% <100.00%> (+7.40%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lpsinger]

@dakota002, I've come around to your original idea. It has many advantages over mine:

• It uses half as much storage space in DynamoDB.
• It will require no database migration.
• In both the Circular auto increment application and the version numbering application, only two tables are involved, not three.

However it does add a bunch of conditional logic, which is a hint that we should be pulling out the common logic and reusing it in two new classes. I am going to propose a couple refactorings in separate PRs that will make this more elegant.

[lpsinger]

At this point, @dakota002, please implement your original versioning algorithm, but by subclassing the base class.

[lpsinger]

What I'm looking for is a new class that extends BaseDynamoDBAutoIncrement and implements the next method. You shouldn't need to modify the existing DynamoDBAutoIncrement class, and you shouldn't need to add a flag to the props.

[dakota002]

What I'm looking for is a new class that extends BaseDynamoDBAutoIncrement and implements the next method. You shouldn't need to modify the existing DynamoDBAutoIncrement class, and you shouldn't need to add a flag to the props.

Sounds good!

[lpsinger]

• Please add a unit test that is analogous to correctly handles a large number of parallel puts, that tests that the locking is working correctly.