Faster change,
with stronger control.
BX-CBP-based offerings reuse banking capabilities through components and APIs. Product composition is defined for each offering. Where microservices and containers are required, BX-CoCore can be evaluated as a separate alternative Main Product.
Bankware Global Adaptive Banking Architecture
The reusable banking engine of BX-CBP-based offerings, built around BX-CBB.
BX-CBP and BX-CoCore are different product architectures, not deployment options of one product. The BX-CBP composition does not transfer to BX-CoCore automatically.
Conventional approach vs Adaptive Banking
Four areas where the approach changes what a project looks like.
| Area | Conventional approach | Adaptive Banking |
|---|---|---|
| Products and rules | Only selected product attributes are configurable | Externalises the product lifecycle and business rules |
| Business logic | Similar logic is duplicated in each program | Reuses standard banking logic through components and APIs |
| Change impact | Many programs and tests change together | Reusable components reduce duplicated logic and help contain the impact of change. |
| Core architecture | Fixed to one legacy monolith | BX-CBP by default; where MSA and containers are required, BX-CoCore can be evaluated as a separate alternative Main Product |
Core architecture options
BX-CBP and BX-CoCore are different product architectures, not deployment options of one product. The BX-CBP composition does not transfer to BX-CoCore automatically.
Separately defined compositions
The composition above applies to BX-CBP-based offerings. These offerings have their own Main Product and product composition; the BX-PF and BX-M or BX-CM rules are not applied to them automatically.
Discuss the Product Foundation.
Tell us about your institution and what you are evaluating.
