Design patterns 101
-
Upload
suvradeep-rudracsm -
Category
Data & Analytics
-
view
119 -
download
2
Transcript of Design patterns 101
1. # 101
The idea behind a design patterns is to learn about its strengths and weaknesses. And
more importantly, understand where and how to use a particular design correctly, so
as to use its strengths properly and overcome its weaknesses.
2. Problem/Intent:
Which partition logic should be used in ORACLE 11g so that we can partition multiple tables together, so that that
related data (FKs) are also stored in the same partition area?
3. Context /Relevance:
Bui lding a high available application a lways needs special database architecture to support fast access and storing of
data. This high availability refers to faster user experience within the organization when the same data is accessed by
di fferent Lines of Business (LOBs) and is distributed across various branches/offices.
This is actually achieve by having a proper data model that is a ligned to the business use case and underlying full
proof partition logic which play a dramatic role as the data increases.
Customer Due Diligence(CDD) solution is built for assessment of customer ri sk as part of Know your customer (KYC)
and Know your Account(KYA) applicant on-boarding and ongoing customer due diligence processes, allowing firms to
better identify, manage, and mitigate customer-related risks.
Customer Due Diligence solution meets the needs of customer onboarding and ongoing due diligence, enabling an
automated, systematic process for the entire customer l ifecycle.
1. Reduce Regulatory Risk
2. Increase Operational efficiencies
3. Ensure consistencies of process
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 business scenario, there is a need where parent-child relationships exists like a Party has KYC related to it
and an account has KYA related to it. Keeping the parent and related child data in one partition will provide
tremendous benefit to a wide variety of applications by improving performance, manageability, and availability. It will
make huge difference when different LOBs with the business access the same KYC or KYA perta ining to the same
Party or Account. One key benefit to reference partitioning is to not have the extra space being used, and not having
to deal with the potential data integrity i ssues.
Reference partitioning improves and simplifies the partitioning of tables that have a parent-child relationship.
The ability to partition by reference removes the necessity for managing the partitions on the child table.
Reference partitioning also eliminates the need to include unnecessary duplicate columns from the parent table
to enable equi-partitioning of the child table.