This project is archived, which means that it's in read-only state; you can download and use this code, but please be aware that it may be buggy and may also contain security vulnerabilities. If you're interested to restore development activities on this project, please email [email protected].

Visit the Glue microsite to learn more about the project through our fully versioned documentation.

• https://glue.finos.org/

Banks are struggling to leverage their existing data residing in heterogeneous ledger systems.

Traditional Data-Warehouse solutions do not provide the performance needed for modern analytical solutions exposed to the end-client.

Banks are in need of a mid & front-office platform allowing them to leverage their data for real time analytical solutions such as Portfolio Risk Management, Performance Analytics forming the basis for the digital transformation.

Glue is an enterprise data model for the buy side, tailored for Wealth and Asset Managers and covering key entities such as Party, Business Relationship, Investment Strategy, Instruments, Portfolios and more.

The model has been designed for strong security, client data protection and GDPR compliance with clear separation of sensitive data, late enrichment and anonymized analytical patterns.

Glue supports high-performance analytical application with appropriate platform implementation and these analytic layers have been implemented in a reference environment with large-scale parallelisation, distributed memory stores and cloud native deployment.

This reference implementation is not part of the data model itself.

The model and implementations like the above support fault tolerance and continuity. This forms the basis of modern, data driven hybrid advisory platforms for clients and advisors with next generation digital experiences.

1. Multilanguage support
2. DB independent scripts

1. Fork it (https://github.com/finos/glue/fork)
2. Create your feature branch (git checkout -b feature/fooBar)
3. Read our contribution guidelines and Community Code of Conduct
4. Commit your changes (git commit -am 'Add some fooBar')
5. Push to the branch (git push origin feature/fooBar)
6. Create a new Pull Request

NOTE: Commits and pull requests to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS.

Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS CLA Bot.

Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.

Need an ICLA? Unsure if you are covered under an existing CCLA? Email [email protected]

Copyright 2020 EPAM Systems, Inc.

Distributed under the Apache License, Version 2.0.

SPDX-License-Identifier: Apache-2.0