Fiorano ESB Reviews

Our primary use case of Fiorano ESB is to expose our core banking APIs. We use Finastra's Fusion Equation, which has its own API layer and runs on an IBM machine. Nowadays, this generation of developers isn't familiar with API structures, so we converted the ESB, which is now working as a middle layer to expose all related core banking APIs via web services. The deployment servers are implemented on-premises, but the configuration is done remotely. 

One of the most valuable features is the scalability. Whenever it's required, we can add more servers and scale. We can actually use specific servers for specific stuff. Unlike in other solutions, now we can implement one server purely dedicated to core-banking-related API. This is very important when it comes to the PCI DSS certification. 

Fiorano ESB could be improved by becoming more user-friendly. Most of the pages and generated reports on API usage are already there, but they could be more user-friendly. There could be more selections added to generate reports. Overall, though, Fiorano suits all our needs and has good functionality. 

I have been using this product for over a year and a half. 

This product seems stable, and there haven't been any incidents where I have had to conduct maintenance. We're new to this, so there is still some tweaking we need to do, and there have been some instances when we expose something to the other party and they find it difficult to get the information. So when it comes to fetching information, sometimes they complain it takes time, so we just have to optimize the process. It's an ongoing effort, but we haven't encountered any major stability or performance issues with the product. 

We have tried to scale it. We implemented it with two or three servers and we recently added one more. Because of the pandemic, most transactions are happening online. At the moment, we just encourage our business to capture more fintechs to come on board to work with the bank. So to accommodate this, we had to add one server. 

There have been some questions and clarifications we have contacted Fiorano's technical team about. They are very helpful and whenever we raise a query, they answer it very quickly. 

The initial setup process was very simple—we aren't going to implement anything complex because those are hard to maintain. Since we have limited solutions, we prefer to implement simple processes. 

At the moment, there are two people working with Fiorano ESB. They handle integration with other systems. For example, if we want to integrate with our internal system and expose APIs, only two people handle it. Once we expose the APIs, we provide the relevant documentation to the relevant party so that they can communicate with the ESB, and it's done.

We implemented through a vendor team. When we exposed APIs to connect our core banking APIs to web services, we had an agreement on the number of services that would be done by the vendor. A certain amount of API exposure was done by the vendor and another amount by ourselves, so it was a hands-on experience. We handled the rest with the vendor's support. 

I don't know the exact numbers, but in our Sri Lankan market, the price is very reasonable. To my knowledge, there was only one other Fiorano ESB implementation in Sri Lanka before our bank. They were keen on working with us because we are a relatively large bank, so they must have given us a better price because of that. 

We also evaluated IBM Integration Bus. When it comes to price and usability, we felt that Fiorano was much more suitable for the bank, which is why we implemented it. We have a limited technical team and IT development staff, so we needed a solution that's very easy to maintain. 

This solution is for online transactions, so it's working 24/7 at the moment. If you are considering implementation and your core banking or other products are running on an IBM platform, Fiorano is the best partner for the platform. 

I rate this solution a nine out of ten because we are satisfied with the product.