Transactional commands — optional Chronicle integration
Command transactions described on this route belong to the optional Cratis.Arc.Chronicle integration, not standalone Arc.
Read Chronicle transactional commands for its commit, rollback, and immediate-append behavior. This compatibility page preserves the previous command-documentation route.
Standalone Arc handlers can call application services and return ordinary values without Chronicle. Arc does not automatically begin a database transaction or roll back arbitrary service writes. For your own lifetime coordination, see command execution scopes.
Choosing an append style
Section titled “Choosing an append style”Continue to Chronicle append styles.
How it works
Section titled “How it works”Continue to Chronicle transaction completion.
Nested commands and aggregates
Section titled “Nested commands and aggregates”Continue to nested commands and aggregate commit boundaries.
Things to know
Section titled “Things to know”Continue to Chronicle transaction limitations.