Design patterns 101
Download as DOCX, PDF1 like496 views
The document discusses the importance of design patterns in database architecture, particularly in relation to Oracle 11g partition logic that enhances high availability applications. It describes a customer due diligence solution that addresses regulatory compliance and operational efficiency by maintaining a single KYC profile per customer and KYA profile per account. The document highlights the advantages of reference partitioning in managing parent-child relationships within databases, ultimately improving performance and data integrity.
Design patterns 101
- 1. 1. # 101 The ideabehinda designpatternsis to learnabout its strengths and weaknesses.And more importantly,understand where and how to use a particular designcorrectly,so as to use its strengths properlyand overcome its weaknesses. 2. Problem/Intent: Which partitionlogic shouldbe usedin ORACLE 11g sothat we canpartition multiple tables together, sothat that related data (FKs) are also storedinthe same partition area? 3. Context/Relevance: Buildinga high available applicationalways needs special database architecture to support fast accessand storingof data. This highavailabilityrefers to faster user experience withinthe organization when the same data is accessedby different Linesof Business (LOBs) andis distributed across various branches/offices. This is actuallyachieve byhaving a proper data modelthat is aligned to the business use case andunderlying full proof partitionlogic whichplaya dramatic role as the data increases. Customer Due Diligence(CDD) solutionis built for assessment of customer riskas part of Knowyour customer (KYC) and Know your Account(KYA) applicant on-boarding andongoing customer due diligence processes, allowing firms to better identify, manage, andmitigate customer-relatedrisks. Customer Due Diligence solutionmeets the needs of customer onboarding andongoing due diligence, enablingan automated, systematic process for the entire customer lifecycle. 1. Reduce RegulatoryRisk 2. Increase Operational efficiencies 3. Ensure consistencies ofprocess The most important business requirement of any CDD project is there should one KYC profile per customer and there should only one KYA profile per account. 4. Solution/Resolution: In the above businessscenario, there is a needwhere parent-childrelationships exists like a Partyhas KYCrelatedto it and anaccount has KYA related to it. Keeping the parent andrelatedchilddata inone partitionwillprovide tremendous benefit to a wide varietyof applications byimprovingperformance, manageability, andavailability. It will make huge difference whendifferent LOBs withthe business access the same KYCor KYA pertainingto the same Partyor Account. One keybenefit to reference partitioning is to not have the extra space being used, and not having to deal withthe potential data integrityissues. Reference partitioning improves and simplifiesthe partitioning of tables that have a parent-child relationship. The abilityto partitionbyreference removes the necessityfor managingthe partitions onthe childtable. Reference partitioning also eliminates the needto include unnecessaryduplicate columns fromthe parent table to enable equi-partitioning of the child table.