Skip to content

Commit

Permalink
Update root .
Browse files Browse the repository at this point in the history
  • Loading branch information
fr33r committed Jan 16, 2021
1 parent 659ced5 commit cbf799d
Showing 1 changed file with 17 additions and 8 deletions.
25 changes: 17 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,24 +25,33 @@ that handles changes when they happen.
- reduced overhead when applying changes.
- decoupling of code triggering changes from code that persists the changes.
- production-ready logs and metrics.
- works with your existing persistence layer.
- automatic and configurable retries.

For SQL datastores, also enjoy:

- one transaction, one connection per unit.
- three queries max.
- additions result in a single `INSERT`.
- alters result in a single `UPDATE`.
- removals result in a single `DELETE`.
- consolidates persistence operations into three operations, regardless of
the amount of entity changes.
- shorter transaction times.
- transaction is opened only once the unit is ready to be saved.
- transaction only remains open as long as it takes for the unit to be saved.
- proper threading of `context.Context` with `database/sql`.

## Release information

### [4.0.0][]

- Introduce `unit` package to alias all types.
- API revamp. Using `work` has never been easier!
### 4.0.0-beta

- Introduce `unit` package for aliasing.
- Reduces API footprint.
- Often "flows" better.
- Introduce retries and related configuration.
- Reconsolidate data mappers abstractions into single `DataMapper` interface.
- Introduce `MapperContext`.
- Alter `Save` to be `context.Context` aware.
- Refactor `work.NewUnit` to dynamically choose which type of work unit to
create based on provided options.
- Reconsolidate uniter functionality.

### [3.2.0][v3.2.0]

Expand Down

0 comments on commit cbf799d

Please sign in to comment.