A transaction boundary groups operations into a unit of work governed by rules for success, failure, concurrency, conflicts, and visibility. Changes commit together when operations succeed and required invariants hold; failures abort the transaction so partial changes do not undermine correctness. section 9.1.1
In a microservice architecture, each service defines its own boundary. A command or query spanning services therefore cannot run as one ACID transaction: participating services perform local transactions. Commands can use a saga; queries rely on multiple independent transactions. section 9.1 section 12.1.5
BEGIN TRANSACTION
SELECT * FROM PRODUCTS WHERE PRODUCT_ID = ?
UPDATE CONSUMER
SET AVAILABLE_CREDIT = AVAILABLE_CREDIT - ?
WHERE CONSUMER_ID = ?
AND AVAILABLE_CREDIT >= ?
INSERT INTO ORDERS (...) VALUES (...)
COMMIT TRANSACTION
A transaction encloses a product lookup, a conditional credit update, and an order insertion, then commits the changes together. section 9.1.1
Treat service placement as consequential: service boundaries also divide processes and transactions. Distributed operations add network failure and availability concerns, so weigh those costs against the design’s needs. section 1.3.4 section 7.5.3

