Keep in mind the product licensing outside of the vendor stack, e.g., if you opt not to use the embedded SQL. If you do a TCO of more than five years, then you will see a big jump in costs for some vendors. Make sure you cater for all environments. We went in with three environments but some businesses that came onboard later on required up to five. This probably depends on the complexity of your business.
When it comes to pricing, I think we cracked a good deal with Broadcom on Layer7. It may be because of the COVID-19 situation. Whatever the reason, from a pricing perspective we have found the solution to be a good deal for us.
We've been using it to program intermittently. There's a problem with one version, which saves pretty slowly. Now it's good. Then we found that this is cheaper. The advantages include the coding, as well as getting emails and alerts from them.
We started off exposing REST APIs to other business units and our external partners by doing legacy integration. The Gateway is a security control point and a way to drive standardisation. Live API Creator is used very successfully by one of our businesses to run all their APIs. Other BUs use the Live API Creator to create the easy, "quick win" APIs, which do not make sense to host on the ESB or where resources are not available to do it quickly. We handle some SOAP services where we are only interested in adding additional security and metrics on top of the SOAP services. We even transform JSON REST to SOAP where legacy internal ESB systems are not able to use REST. We have seen a huge uptake in routing messaging services, like SMS and WhatsApp. The Gateway currently serves to standardise these into a single API view with multiple channels.