Download to read offline
arctitecture application system design os dsa
- 1. Application Architecture “How Common BusinessNeeds Shape Reusable Software Architectures”
- 2. Where Do They ComeFrom? • Application systems are built to meet business or organizational needs • Common across businesses: • Hiring • Invoicing • Accounting • Sector-specific functions: • Phone companies call metering, → billing, network management • This shared functionality leads to reusable architectures
- 3. Where Are TheyUsed?
- 4. Why Are TheyUsed? 01 04 02 05 03 06 Starting Point for Design Checklist For Consistency Organize Team Development Component Reusability Shared Vocabulary Common Practice
- 5. Example:Transaction Processing Systems CoreConcept Designed For • A transaction is treated as an atomic unit • All operations must complete successfully • Or none are applied → ensures database consistency Designed to handle user requests for data retrieval or database updates • Withdrawing money from an ATM • Check balance • Deduct amount • Dispense cash • Only then update the database Example
- 6. Technical View User VsTechnical Transactions • Atomic unit of work • Multiple DB read/write operations • Must be completed fully or roll back • Coherent of actions sequence • For e.g. “Find all flights from London to Paris”. • May not require DB permanent change. User View
- 7. Structure of TransactionSystem
- 8. Conclusion A smart designtoday ____ scalable & maintainable system tomorrow.