A compact library for tracking and committing atomic changes to your entities.
What is it?
work does the heavy lifting of tracking changes that your application makes
to entities within a particular operation. This is accomplished by using what we
refer to as a "work unit", which is essentially an implementation of the
[Unit Of Work][uow] pattern popularized by Martin Fowler. With work units,
you no longer need to write any code to track, apply, or rollback changes
atomically in your application. This lets you focus on just writing the code
that handles changes when they happen.
Why use it?
- easier management of changes to your entities.
- automatic rollback of changes when chaos ensues.
- centralization of save and rollback functionality.
- 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.
- 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
unitpackage for aliasing.
- Reduces API footprint.
- Often "flows" better.
- Introduce retries and related configuration.
- Reconsolidate data mappers abstractions into single
work.NewUnitto dynamically choose which type of work unit to
create based on provided options.
- Reconsolidate uniter functionality.