Thanks to an Operational Data Store delivered by Adastra, a major Czech bank has acquired a flexible data repository for the real-time integration of key data from its operational processes, including support for cleaning and consolidating this data.
Solution to a problem
As a result of ever-increasing functional requirements, the customer came to the conclusion that their previous IT architecture had ceased to be effective, and so began to search for a better solution. The choice fell on Adastra’s Service-Oriented Architecture, and the bank then successfully underwent a technological revolution that has placed it among the most technologically advanced Czech banks.
The Enterprise Service Bus (ESB) connecting the constituent parts of the bank’s systems became a central element of the new solution. However, the integration of functions accomplished by the ESB was only one side of the coin, as the question of data also had to be addressed. This second aspect could be handled by creating a central data repository to support work with operational data, thus rendering the solution truly effective and eliminating wholly unnecessary data flows, including possible data inconsistencies between systems. But how to create this kind of repository?
An Operational Data Store is a somewhat paradoxical architectural component: a lot of people know about it, a lot of people talk about it, but few really understand it. This has a highly detrimental effect on the success of ODS implementations. Fortunately, this was not the case with this particular client.
Description of the solution
The answer to our earlier question is an Operational Data Store that supports real-time data integration. We used Oracle Database as the database platform, along with RAC to ensure high accessibility. We created the ODS data model on the basis of the Adastra Banking Data Model. We set up the technological integration with ESB in accordance with the customer’s technical standards.
The most interesting part of the solution is the use of Model-Driven Development to create tables, APIs, and ETLs. All listed structures and transformations are generated from metadata stored in the CASE tool Sybase PowerDesigner. Thanks to recommended patterns and best practices, this approach offers maximum standardization across the entire solution, high flexibility, easy maintenance, and extremely advantageous performance.
300
The bank’s ODS data model consists of 300 very carefully selected and designed tables.
Project outcome
The client successfully uses our Operational Data Store implementation to support its operational processes. Long term, the solution has proved itself to be exceedingly effective and flexible, and can easily be extended to provide new functionalities in order to simplify the client’s IT architecture. In addition to delivering changes more efficiently, this simplification also leads to lower IT costs.
In Adastra’s ODS, the bank has thus acquired an effective and efficient data platform capable of integrating data in real time and delivering them simultaneously to operational processes and the data warehouse. In the future, the ODS will greatly facilitate the implementation of any Master Data Management (MDM) solutions. Close integration with the data warehouse ensures consistency between operational processes and reporting.
450
The ODS flawlessly handles more than 450 API calls per second in the bank.
Who participated in the project
Our excellent reputation is built by competent people who bring our projects to a successful end. In this case, the client relied on these consultants.
Vlastimil Bažant
Consultant
Stanislav Kaczor
Consultant
Jaromír Mataj
Solution Architect
Are you interested in a similar solution? Contact us.
Thank you
We will contact you as soon as possible.