Backbase working with Financial Instituitions
Backbase has created an enterprise web framework that empowers developers, business and End Users.
The concept here is to create a framework which provides a unified experience across all platforms such as Mobile and Web with a lean, simple and cost-effective solution.
For IT developers, it has created a framework which can provide inbuilt security and easy integration to the system present.
For Financial institutions, they have a concept called CXP manager which helps the Credit Unions to manage the webpage according to their needs without many dependencies on IT team.
As for customers, the idea of Omnichannel supports helps them get the best User experience with multi-device access anywhere they want.
The Technical Facts:
So Backbase has divided itself in two sections when it comes to the technical end namely Front End and the Back End.
Front end takes care of the User Experience part i.e. whatever needs to be shown to the user to use and access it. It has support to Angular JS for Widget Collection 2 architecture version 5.7 and Angular 4 with Widget Collection 3 version 6.0.
One interesting thing about Backbase is that it supports widget architecture rather than the conventional portlets architecture.
Now the difference between a widget and a portlet is that in a widget, most of the work happens on the client side whereas in a portlet most of the work happens on the server side.
Another good thing about Backbase is that it upgrades itself to the latest version of Angular every now and then. It has also adapted the concept of components which makes the code highly reusable.
On the other hand, the backend takes care of security, login, connecting to API’s, bringing data to the Front End etc.
For this, Backbase supports REST architecture for interoperability which uses Spring Framework and Apache Camel. Also, they use a concept called RAML (Rest API Markup Language) for data flow from backend to front end.
Another interesting fact here is that it supports Internationalization. This means it supports a key-value structure so that the portal can easily adapt to any specific local language based on the region.
Now everything in Backbase runs on 4 different servers each serving their own purpose which are Portal Management, Content Management, Search Operations and Management of all the servers.
There can be 3 Opinions here, each from one end i.e. User, Financial Institution and Developer.
From a User End, Omni Channel support does most of the magic which brings seamless experience throughout the application.
For Financial Institution, Backbase for Credit Unions provide CXP manager which has given good freedom to manage the portal effectively.
And lastly from a developer’s point of view, if Backbase is used at its full capacity, it can create wonderful web applications with minimum efforts as most of the logic is already provided by the Backbase widgets.
Though we have quite advantages, there are a couple of things that bugs’ a developer the most.
First is the use of the 4 server architecture. This leads to quite a heavy load on the developer’ system which requires a RAM size of 16GB for running Backbase efficiently on Windows, which is quite high.
Secondly, for any change in the backend code, we are required to restart the Server. This consumes quite a lot of time. Though they have introduced a concept called ‘Backbase Watch’, it is still heavy on the system as well as a bit time consuming for the developers.
Though Backbase has some dropdowns from a developer’s perspective, it has quite many advantages as a product because of which it becomes a feasible option for everyone. It’s easy to migrate, code and implement.
It has a great result for the end user which leads to good business for the Credit Unions. So everyone is on the win-win side here. I would recommend going ahead with this product if you are looking to migrate your portal and searching for a good framework.