Journey to open platform for digital bank modernization. A reference implementation of BIAN to start, providing documentation and artifacts of reusable source code.
Apache License 2.0
15
stars
9
forks
source link
Business domain to technical components mapping #121
Two parts:
1) Improve documentation on how BIAN domains and services (e.g. Customers > Party References > Legal Entity Directory) map to components that are auto generated (projects, application services containers and kafka brokers)
2) Add a feature to to define the granularity level of BIAN services when they get deployed as technical components
Using the Channels domain as an example:
"Information providers" could have all services and broker bundled in the same project and sharing the same broker
"Chanel Specific" could have "ATM Network Operations" as a separate project and broker to isolate load and failures
"Chanel Specific" could have all other sub-sub-domains bundled in the same project
"Servicing" and "Distribution" sub-domains could be bundled in the same project
The goal is having a flexible and configuration driven approach to define the boundaries for the components rather than aligning that to a BIAN domain, sub-domain or sub-sub-domain
For 2) the deployment operator could look for a configuration file and based on it create projects / applications / brokers as per defined grouping. If the file was not available, the traditional BIAN domain aligned deployment would take place
Feature Request
Description of Problem:
Two parts: 1) Improve documentation on how BIAN domains and services (e.g. Customers > Party References > Legal Entity Directory) map to components that are auto generated (projects, application services containers and kafka brokers)
2) Add a feature to to define the granularity level of BIAN services when they get deployed as technical components
Using the Channels domain as an example:
The goal is having a flexible and configuration driven approach to define the boundaries for the components rather than aligning that to a BIAN domain, sub-domain or sub-sub-domain
Potential Solutions:
For 1) the documentation may need to be updated regarding the current as-is state: https://github.com/open-accelerators/mercury/blob/main/mercury-framework/README.md https://github.com/open-accelerators/mercury/blob/main/mercury-operator/README.md
For 2) the deployment operator could look for a configuration file and based on it create projects / applications / brokers as per defined grouping. If the file was not available, the traditional BIAN domain aligned deployment would take place