Smaller banks, unable to compete on scale, will be drawn to trusted advisor, serving niche markets with a deeper understanding and empathy of their needs. In the Australian market, Judo is perhaps a standout with its approach to SME banking. Others include Newcastle Greater who continues to build a strong community franchise in and around the Hunter Valley.
As these two trends of technologisation and separation build momentum, new patterns of manufacture and delivery are emerging. These include Bank as a Service, Composability and Personalisation. The first is the development of generic banking services, offered in the cloud, on a subscription basis to those who don’t have the economics or desire to build out generic services, wishing to focus their capital on their value-added differentiators, renting the rest in an elastic, Pay As You Go, manner. Composability is a term borrowed from the manufacturing industry and automotive in particular. VW are particularly good at it, whereby a small number of core chasses are built which are then made to look like a plethora of models and brands on demand. These come off the factory floor in line, each car different from the last. Composability creates scale and agility, key attributes in any manufacturing operation today, including finance and the ability to personalise the customer experience to the segment of one.
A New Technology Architecture
Bank as a Service and Composability require a purpose-built technology architecture. This architecture is cloud native, engineered using microservices. Rather than simply moving legacy software to the cloud, whilst retaining legacy compute models, cloud native software is engineered to fully harness capabilities, efficiencies, and scale, such as those offered by Kubernetes and a serverless paradigm.
There have been numerous attempts to shift legacy straight to the cloud. These don’t tend to go well, due to the mismatch of technology paradigms. Up until about 10 years ago, software was built in a highly monolithic way, with components highly dependent on the availability and nature of others. This severely impacts agility and their ability to operate effectively in the cloud.
The more loosely coupled the software, the faster change can occur and the more composable the services offered. The journey to lose coupling commences by organising organisational capabilities across the four key systems of connection, intelligence, operation and enablement. With these isolated, individual components can then begin to be presented as microservices.