Composability describes how independently developed components can work together through compatible interfaces. In Web3, an application can call existing smart contracts and use their tokens, liquidity, or accounting functions. Developers can build on established components without rebuilding every underlying service.
Combining actions in one transaction
For example, a contract might exchange one token through a decentralized exchange and then deposit the received token into a lending protocol. If these actions run within one transaction and a required step fails, the transaction can revert the preceding contract changes. This all-or-nothing execution is called atomic composability.
Compatibility still matters. Token behavior, access permissions, available liquidity, and contract interfaces must fit the intended workflow. Sharing a blockchain does not make every contract automatically compatible, and separate transactions do not inherit the same atomic guarantee.
Reuse also creates dependencies
A composed application depends on the behavior of its components. An oracle failure, contract upgrade, paused withdrawal, or exploited protocol can affect applications built on top of it.
Security review must therefore consider the combined interactions, not only each component in isolation. Composability enables useful services and faster development, but it can also connect risks that appeared separate when the individual protocols were examined alone.