The OpenLegacy platform builds multiple transactions, screens, or even systems into a single API. This combination allows users to build Smart System APIs instead of low-level APIs that then need to be combined to build anything useful. Tibco requires building low-level system APIs first. These low-level APIs support only a single mainframe transaction or screen. The low-level system APIs waste time and resources since they require a rigorous testing process during deployment. Furthermore, hosting the additional APIs takes up valuable core resources. At run-time, queueing data just to pass among APIs wastes run-time resources as well. A much better way to develop APIs is to build them based on a business need or purpose.
“My problem is not budget, or need - every group in the bank, across every channel, is asking for API integration and services. My problem is the ability to scale up and execute at the velocity of what we need to achieve in the short and long-term."