atomicity- changes to the state are atomic (indivisible). ‘all or nothing’
consistency- any transaction will bring the db from one valid state to another. must be valid according to all defined rules- constraints, cascades, triggers, etc. any action within transaction is the correct transformation of the state and does not violate any integrity constraints associated with it
isolation- even though transactions occur concurrently, it appears to have order?
durability- once a transaction is committed, its changes to the state survive failures