# Architecture principles whose scope is state_transaction

> 8 records

This index as JSON: https://banes-lab.com/json/api/facets/architecture/scope/state-transaction

## Entries

- [Big Ball of Mud](https://banes-lab.com/records/architecture/big-ball-of-mud.md): A defect in which a system has no discernible boundaries, so any part can depend on and change any other.
- [Hardcoded Configuration](https://banes-lab.com/records/architecture/hardcoded-configuration.md): A defect in which environment, credential or policy values are written into code instead of being supplied as configuration.
- [Shared Mutable State](https://banes-lab.com/records/architecture/shared-mutable-state.md): A defect in which writable state is shared across modules with no owner and no synchronization.
- [Distributed Monolith](https://banes-lab.com/records/architecture/distributed-monolith.md): A defect in which services are deployed separately but still share data, transactions and release cycles.
- [Ambient Context](https://banes-lab.com/records/architecture/ambient-context.md): A defect in which request, tenant or user state is read from implicit global context.
- [Transaction Script Sprawl](https://banes-lab.com/records/architecture/transaction-script-sprawl.md): A defect in which business processes are procedural scripts that coordinate validation, persistence and decisions directly.
- [Lost Update](https://banes-lab.com/records/architecture/lost-update.md): A defect in which concurrent writers overwrite each other's changes without a version check.
- [Big-Bang Release](https://banes-lab.com/records/architecture/big-bang-release.md): A defect in which a large, irreversible change reaches every user at once, with no staged rollout.