# `StatifierPersistence.Serialization.AdapterLock`
[🔗](https://github.com/riddler/statifier_persistence/blob/v0.18.0/lib/statifier_persistence/serialization/adapter_lock.ex#L1)

The default `StatifierPersistence.Serialization` strategy (ADR-0004
decision 5): per-execution ordering as the storage adapter's own lock.

Its `config` is the `StatifierPersistence.Storage` handle itself.
`with_execution/3` delegates to the adapter's optional
`c:StatifierPersistence.Storage.Adapter.lock_execution/3` when the adapter
exports it, and refuses with `{:error, {:serialization, :not_supported}}`
when it does not - an adapter without a lock provides no ordering, and
a silent fallback here would be the loop pretending otherwise.

---

*Consult [api-reference.md](api-reference.md) for complete listing*