Object Oriented Software Engineering View all facts Glossary Help |
| subject > pattern > architectural pattern > transaction-processing |
| transaction-processing | ||||
| subject | fact | |||
| transaction-processing | contains a process which reads a series of inputs describing a transaction one by one, and a transaction handler that decides what to do with each transaction, and which dispatches a procedure call or message to a component that will handle the transaction | ![]() |
| has definition An architectural pattern in which a transaction dispatcher inputs transactions and dispatches them to handlers | ![]() | |
| facilitates divide-and-conquer since the design of each handler can be given to separate software engineers | ![]() | |
| is a subtopic of 9.5 - Architectural Patterns | ![]() | |
| is a kind of architectural pattern | ![]() | |
| architectural pattern | allows you to design flexible systems using components that are as independent of each other as possible | ![]() |
| pattern | should be as general as possible | ![]() |
| should be described in an easy-to-understand form so that people can determine when and how to use it | ![]() |